Moritz Klack

Can you check your codesandbox? It seems to be the easy connect example.

The issue here is that you are passing the nodes from elk back into React Flow. I adjusted your code, so that it only takes the position from the layouted...

I think the issue here is that you are creating a new nodes object on every render. Could you change that and see if it fixes the issue?

We implemented this exact use case in our [react-flow library](https://github.com/wbkd/react-flow). It looks something like this: 1. wrap all draggable elements with DraggableCore (you always need to store all positions of...

We will check this again for the Svelte Flow 1.0.0 / Svelte 5.

Could you give us some more context? What are the initial positions of your nodes and what are your `snapGrid` values?

Ok, I can see it now. This is not intended. We will try to have a look and fix it.

I will leave this open for now and have another look. I think we are closer to a fix now that the position change is not fired anymore.

@corbinklett this sounds like a race condition. It was a bad idea to mix up the user selection stuff with the dragging behaviour. However I would like to understand the...

What is happening here? First of all the internal nodes should only be used internally. Every node that gets passed to `nodes` or `defaultNode` should be a regular node. If...