Wrong events x / y values when not hovering the sigma instance #1169
Comments
jacomyal
added a commit
that referenced
this issue
Nov 29, 2021
Details: - Updates mouse-manipulations example so that it features a sigma container in a draggable page (to make it easier to test d-n-d code as well as zooming in a graph in a scrolled webpage) - Removes getX and getY helpers - Makes `dom` a required argument in the getPosition helper, and adapts all calls to this helper everywhere in the codebase - Replaces pageX and pageY with clientX and clientY in getPosition (to fix it) This commit fixes issues #1175 and #1169.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am developing an application where the sigma container has panels around. In this app, nodes are draggable, using a code very similar to the one in the
mouse-manipulationsexample.Since the v2.1.0, users can drag the node, even when the mouse leaves the container, thanks to the #1148 fix.
But now, when the mouse leaves the container, the nodes are no more under the mouse, because the x and y positions in the event depend on what's under the mouse, basically.
The solution is to stop using the
getXandgetYpositions, and instead always use the better offset method.The text was updated successfully, but these errors were encountered: