Results 15 comments of Saki

The issue has been fixed and will be released in the upcoming `5.6.12` version.

This issue will be fixed with the fix of https://github.com/bryntum/support/issues/8973

As @SergeyMaltsev said "Our components are not compatible with SSR" and that has no immediate "fix." Our components do need a browser environment to work. Therefore, if you can prevent...

Not reproducible with Bryntum version 6.0.2 and Vue 2 version 2.7.16. Closing the ticket.

I have re-investigated the ticket and I found that it is not reproducible with Vue 3.2.13 and Bryntum 6.1.3 versions. I'm attaching the new showcase. [inline-data.zip](https://github.com/user-attachments/files/17702030/inline-data.zip)

The problem here is related to the "double run" of the React 18+ application in strict development mode. In this mode React (not Bryntum) starts the application, then immediately stops...

@juanprog97, interesting. I'll check that. The mystery is that the store is destroyed. I'll post here the results.

@juanprog97 preliminary/incomplete: The problem lies in the asynchronous renderer (configBryntum.tsx:59). If you could make it non-async it could help as a workaround. However, I'll discuss it with a developer who...

@juanprog97, as you can see, we have fixed the crash, however, the renderer code is still complex and can introduce some racing conditions or unwanted behavior. The idea of renderer...

Here is the summary of what is happening here: 1. If `constrainDragToTimeline` is `false` then a clone (a proxy) is created for dragging and the proxy is dragged while the...