Moritz Klack

It's weird that you are using Redux to manage the nodes state and use `useNodesState`. I could imagine that this is part of the issue here. You should only use...

@Manuelbaun there are some edges that are invisible or do you get a warning "couldn't create edge .."?

We revised the rendering for nodes and edges in v12. If the issue still occurs, please re-open with a codesandbox or repo.

Not sure if we can do anything about it. Does this also happen when you are not using `fitView`?

I checked this again and it's not something we could solve on library side. It seems to be a sub pixel rendering issue that might be better if you would...

Please provide a codesandbox for this: https://new.reactflow.dev

Could you create a codensadbox for this? https://new.reactflow.dev

There is no need to collect selected nodes/ edges on your side. You can iterate over nodes / edges and get all items that are selected. If have no state...

Please re-open if it's still an issue.

This is fixed in v12 and we won't fix it for v11. The namespace doesn't solve it unfortunately.