Moritz Klack

Fixed with React Flow 12! If you are using 11, you can find the migration guide here: https://reactflow.dev/learn/troubleshooting/migrate-to-v12

you can do `panOnDrag={[2]}` so that the second mouse button is for activating dragging. Does it work?

Is this a bug? We need to check if this is really not working in the latest version.

I can confirm that this is not working. But I am also not sure what to do about this. `panOnDrag=[1]` doesn't change anything about how you can drag nodes either...

That's a good question @hiepnguyen3001. Unfortunately this is only possible with a workaround. You could listen to the selection key and set `nodesDraggable={false}` for example. Would that work?

Damn.. The only way I see then is to add a class or set a style directly that prevents all pointer events.

If you need this feature, the workaround is to set `pointer-events: none`.

Does this issue happen with any of the examples on the website?

I guess the issue here is that you are creating new nodes. This would not happen if you would iterate over your existing nodes and not throw away any information....

@EzraBrooks is still an issue for you or could you fix it by upgrading to React Flow 12?