Moritz Klack

Thanks for bringing this up! I tried to set the cursor explicitly and `user-select: none` but none of that worked. If anyone has an idea how to solve this, please...

Hey @datoslabs we don't want to trigger a `onNodeDragStop` on click. That's why we return early here. Could you explain how to reproduce the issue with the non triggered drag...

Yep you got a point here.. maybe we can tag this for v10 since it would be a breaking change.

Hey @cliffordfajardo this is a very good idea! Thanks, we will pin it :) I think you meant ".. that use React Flow ..." instead of "..that use graphin ...".

Hey @adhammo thanks for your input here. Unfortunately we have little resources at the moment so PRs are highly appreciated :)

Everything would be easier if we would have a different API for the handles. How could we get the `isValidConnection` function out of the custom node component? I like your...

Do you need the `onMouseDown` event for the whole node? You can add the class name `nodrag` to disable the drag behaviour (that also enables `onMouseDown`).

If you want to use `onMouseDown` inside a node you need to use `onMouseDownCapture`. Explanation: https://github.com/d3/d3-zoom/issues/66#issuecomment-255175895 Does that work for you?

This is harder than I thought 🤔 When the drag handler starts, d3-zoom adds mousemove and mouseup to the window (when I get it right) and our mouseup handler don't...

Did you try do add the effect with CSS or do you need JS for it?