Pointermove fires only once in Device Mode
Reported by
jay.dunn...@jmrapidapps.net,
Dec 12 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14 Steps to reproduce the problem: 1. Create an HTML document with a div. Attach a pointermove event listener to the div that writes to the console log when invoked. 2. Open the document in Chrome. 3. Open the Dev Tools Console. (Disable Device Mode.) 4. Move the cursor over the div. Many pointermove events will be generated. 5. Switch to Device Mode and select any device. 6. Move the cursor over the div, press the pointer button, and move the cursor. Only one pointermove event will be generated. What is the expected behavior? In both Device Mode and normal mode, pointermove events should be fired at approximately the same rate as mousemove or touchmove events. What went wrong? In Device Mode, pointermove events appear to be fired only once rather than continuously. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Issue also exists on Windows. In Device Mode, pointer move events are fired only when the pointerdown event was on the same element. It makes sense that Device Mode pointermove events would only fire during a simulated touch, but I do not know whether they should fire if a touch moves into an element with a pointermove listener.
,
Dec 12 2016
@tdresser: is that an expected behavior (getting a single pointermove when moving a touch)?
,
Dec 13 2016
This sounds like it's working as intended to me. Apply touch-action:none if you want to continue getting pointermove events and disable scrolling.
,
Dec 13 2016
Yes. This is an expected behavior. As Tim pointed out you need to add touch-action:none to the element underneath the touch if you don't like the user agent consider touch movements as any gesture. In your case if you have listened to all the event, what you actually received was pointerdown, pointermove, pointercancel. The last pointercancel shows that the touch is now being handled by browser and its normal events are not going to be delivered to the page. Does this address the concern? |
||||
►
Sign in to add a comment |
||||
Comment 1 by chenwilliam@chromium.org
, Dec 12 2016Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)