Chrome Android delay and mousemove events #981
Comments
wytrych
added a commit
to wytrych/Sortable
that referenced
this issue
Oct 20, 2016
When using drag delay, the event is cancelled on a series of events, including `mousemove` which seems to be always fired on Chrome Android, even in cases when `touchmove` doesn't fire. This cause the drag to never commence when using the delay property. See SortableJS#981
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is an issue with dragging when the
delayproperty is set on Chrome Android. What happens is that themousemoveevent, which cancels the drag https://github.com/RubaXa/Sortable/blob/f4f1ad395bfdacdb71f1e4b54a39a5791d5feb86/Sortable.js#L437 always seems to fire on Chrome Android, (see https://bugs.chromium.org/p/chromium/issues/detail?id=119216), even if I keep my finger really still. It doesn't trigger thetouchmoveevent, because if I comment out that line withmousemoveit works perfectly fine.So the bottom line is: Dragging never starts on Chrome Android if the
delayproperty is set to anything greater than 0Not sure if there can be a good solution for this, other than removing the
mousemoveline which IMO isn't really required since it is not standard behaviour to press the mouse button and then move it around a lot, but maybe I'm wrong. I have been experimenting a little bit how to fix this issue, but all other solutions have unwanted side effects. Any ideas?The text was updated successfully, but these errors were encountered: