pointercancel event is fired with clientX and clientY set to 0
Reported by
grl...@gmail.com,
May 18 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. Open desktop chrome and activate mobile emulation OR open chrome on an android device 2. Open https://jsfiddle.net/xpsom5j5/1 OR the attached file in chrome 3. Click down/touch and drag the red rectangle until a pointercancel event is fired What is the expected behavior? If/when the pointercancel event is fired, the clientX/Y values should correspond to the current coordinates of the pointing device What went wrong? The clientX/Y values are set to zero Did this work before? N/A Does this work in other browsers? Yes Chrome version: 57.0.2987.133 Channel: stable OS Version: 6.3 Flash Version:
,
May 18 2017
I don't believe we initialize the offsets on a pointercancel event. I'm not sure what use it really is since it is a async notification the pointer didn't actually get removed at the point we just know scrolling started and to send a pointercancel. Navid, do you want to figure out what other vendors do and write some interop tests around this? |
||
►
Sign in to add a comment |
||
Comment 1 by luke.a.p...@gmail.com
, May 18 2017