Moritz Klack

Please re-open if the issue is not fixed in the latest version (12.x.x)

Hey @RunDevelopment I will check your PR now. I think, that we made a mistake by allowing users to use these functions for controlled flows. They were only meant to...

Thanks for your help! This was a good fix for the issue and you are right, that it's very convenient to have these helper functions.

released in v10.2.3

Can you create a codesandbox for this? I can't repro your issue: https://codesandbox.io/s/summer-pine-vvt7h6?file=/src/NodeResetter.tsx:175-233

great that you could solve it :)

That's a bit weird indeed and shouldn't be the case. I will take a look.

I didn't know about this. Thanks for the hint we need to see what we can do about it. For now you could do `nodesFocusable={false}` in order to prevent `role="button"`...

Now that I look at this issue again, a better default for nodes and edges might be: role="group" aria-roledescription="node" / "edge" We need to check if this could solve this.

Since React Flow 12.7.0 nodes and edges use "group" as a role. You can change this by using the new `ariaRole` option. Thanks @printerscanner 🔥