You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The equivalent of d3/d3-brush#18, but for d3-zoom. If the browser fails to deliver a mouseup (or touchend or touchcancel) event, the active gesture can get orphaned, in which case no new gestures can start or end.
The text was updated successfully, but these errors were encountered:
(closes#2151), (see also d3/d3-zoom#60, d3/d3-brush#18)
Intercept `mousedown` and check if there is an orphaned zoom gesture.
This can happen if a previous `mousedown` occurred without a `mouseup`.
If we detect this, dispatch `mouseup` to complete the orphaned gesture,
so that d3-zoom won't stop propagation of new `mousedown` events.
May I get an update on this? This affects all of my scripts that use d3.zoom() when accessed via mobiles/touchscreens. When the user pinches to zoom in/zoom out, and then tries to pan by dragging with a single touch, the program behaves as though two fingers are still touching the screen - i.e. it doesn't fire a touchend/touchcancel event, or enough touchend/touchcancel events.
The bug occurs in iOS and Android, across all browsers I tried (though I wasn't exhaustive).
The equivalent of d3/d3-brush#18, but for d3-zoom. If the browser fails to deliver a mouseup (or touchend or touchcancel) event, the active gesture can get orphaned, in which case no new gestures can start or end.
The text was updated successfully, but these errors were encountered: