Issue metadata
Sign in to add a comment
|
Missing pointerDown event if using (thumb) pen on touch screen
Reported by
chaotoma...@googlemail.com,
Aug 22
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: 1. Attach an eventlistener for 'pointerDown' events (on any dom element) 2. Drag with a thumb over the screen (e.g. on Surface or Legamaster) 3. Inspect all dispatched events using `monitorEvents(document.body)` What is the expected behavior? Like with a mouse pointer (or a finger on the touch screen or a pen) the browser should dispatch `pointerDown` (maybe `pointerMove`) and `pointerUp`. What went wrong? The `pointerDown` isn't logged and the related event listener is not called. touchStart is triggered but I need pointerDown since I need the information of "event.buttons" which should be "32" for a thumb. Instead I get an initialil pointerMove with this flag. I can handle not having a pointerDown for now but it would be great to have this fixed. Did this work before? Yes M67 (as far as I know, maybe also M66) Does this work in other browsers? Yes Chrome version: 68.0.3440.106 Channel: stable OS Version: 10 Flash Version: For debugging this problem open this codepen on a touch devices supporting pens and thumbs (e.g. a surface): https://codepen.io/Chaoste/pen/WyPqGB
,
Aug 23
chaotomat2009@ Thanks for the issue. Tested this issue on Windows 10 Surface Pro 4 on the reported version 68.0.3440.106 and the latest Canary 70.0.3530.0 and unable to reproduce the issue by following the below steps. 1. Launched Chrome and navigated to https://codepen.io/Chaoste/pen/WyPqGB. 2. Dragged with thumb,pen over the screen and could observe that the `pointerDown` event is logged. Attached is the screen cast for reference. Request you to check and confirm if anything is missed from our end in triaging the issue. Also request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations. Thanks..
,
Aug 30
Closing this as we were not able to reproduce this and there was no feedback from the reporter. Reporter, feel free to comment here or open a new bug if you get the information requested.
,
Sep 5
Hi susan, thanks for your feedback and screencast. I did some more testing and I'm now able to define this problem more specific. When I tested this in my application back then I didn't receive "pointerDown". I was able to reproduce it in my codepen because I didn't add "touch-action: none;" (my application did). For some reason the browsers native touch behaviours (which were not blocked in my codepen) block some of the pointer events. We checked in Edge, Firefox and the latest Chrome version. As you can see in your screencast it ends up missing a "pointerUp" event. For me it's frightening that something so stable as the pointer API just doesn't give some events. It would be better to receive all events even if the browser handles it in a way (not stopping propagation). At least every "pointerDown" should always follow a "pointerUp" and vice versa. Generally advice if someone faced related problems: -> Always block browsers pointer handling. So using a real thumb / eraser tool on a touch screen (Legamaster in my case) on an element with "touch-action: none;" didn't dispatch "pointerDown". This seems to be fixed with the latest version. However I still believe that this was a bug in the above mentioned v68. I extended my codepen to also log "event.buttons" so one can see if the browser actually recognizes the eraser (buttons=32) because it worked if it only recognized a pen tool. Thanks for your response. I guess this ticket can be closed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Aug 23