onNodeClick triggers when panning the graph and releasing where node was

[krumpyzoid]

Describe the bug
When panning the graph, if you release the mouse where a node was when you started panning, it'll trigger the onNodeClick callback even though the node is not there anymore.

To Reproduce

1. Click anywhere to start panning
2. Drag and release where a node was before you started panning
3. onNodeClick should fire

Expected behavior
onNodeClick should only fire if you actually click on the node

Screenshots
https://github.com/user-attachments/assets/49139203-1e9a-450a-b419-fec05a0648e8

Desktop (please complete the following information):

• OS: macOS
• Browser : Arc (chromium)
• Version: Version 1.85.1 (59724) / Chromium Engine Version 134.0.6998.45

Additional context
We are using a setup with text labels as nodes, extremely close to the example in the documentation. Therefore we do have a nodePointerAreaPaint callback.

[vasturiano]

@krumpyzoid thanks for reaching out.

I've applied a patch that fixes this issue on the underlying lib force-graph. So if you upgrade force-graph in your dependency tree to at least 1.49.4 you shouldn't experience this issue anymore.

[krumpyzoid]

Thanks for the quick update. Fix works great.

It's still possible to grab the node for ~0.2s after releasing the drag, but it's not firing the onNodeClick callback and you really have to be fast to grab the node, so I can live with that.

Enregistrement.de.l.ecran.2025-03-14.a.09.40.28.mov