Mousemove and mouseup for drag and drop in JS
Reported by
klaus.sc...@gmail.com,
Jan 19 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:50.0) Gecko/20100101 Firefox/50.0 Steps to reproduce the problem: 1. Create a mousedown listeners 2. On click, register a mousemove listener on body 3. On mouseup remove move listner What is the expected behavior? The mousemove event is fired while moving until the mouse is released. The mouseup event is fired. What went wrong? This used to work until two days ago on android and desktop. Now it stopped working on android. The mouse events are not fired, except the mousedown. Check our the ULR below. If you open it on a PC, you can drag and drop the wheel . If you open in a Android it does not work any more. https://quant-ux.com/test.html?h=a2aa10ahiF9hgacAmPyBSMwdJSHOuyLm4IZ1N1GY7uA72cytFPVJ6tMisZse&log=false Did this work before? N/A Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: OS X 10.12 Flash Version: This will break a lot of JS drag n drop libs!
,
Jan 19 2017
Hi klaus.schaefers@gmail.com: Please give us a bit more details: - Which version of Chrome used to work on Android (chrome://version)? - And which version doesn't work now? - Did you really mean adding mouse event listeners and not touch events? Mouse dragging never produced mousemoves on Android IIRC.
,
Jan 19 2017
a) I use Version 55.0.2883.95 (64-bit) b) Since yesterday c) I used dojo/touch touch.move which did some magic in the back. This stopped working now. In the release notes (https://chromium.googlesource.com/chromium/src/+log/56.0.2924.28..56.0.2924.67?pretty=fuller&n=10000) I saw: Reroute Android mouse events to touch event path. This is a partial revert of crrev.com/2054193002 that aimed to make Android mouse events more logical & consistent. However, that change made few UI activities impossible through mouse, like text selection, zoom & scrolling. Until we fix those for mouse, we are re-diverting mouse events to the touch-event path through this CL. BUG= 678756 I assume this causes the issue
,
Jan 20 2017
Android mouse changes we attempted is not relevant here because it affected M56 beta only. This is related to PointerEvents (lauched in Chrome 55). Either your Chrome or dojo got updated to use PointerEvents after you last checked your prototype. With PointerEvents, the page doesn't get any pointermove once browser starts scrolling the page. Adding "touch-action: none" style to .MatcScreen fixes the problem which tells the browser not to scroll that div. |
|||
►
Sign in to add a comment |
|||
Comment 1 by dtapu...@chromium.org
, Jan 19 2017Owner: mustaq@chromium.org
Status: Assigned (was: Unconfirmed)