- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Dec 2022 17:30:11 +0000
- To: public-pointer-events@w3.org
mustaqahmed has just created a new issue for https://github.com/w3c/pointerevents: == Coordinates of a `pointercancel` event == I think the spec should say that the coordinates of a `pointercancel` event are uninitialized (or zeros). Chrome does not initialize the coordinates of a `pointercancel` event, which seems logical because the event is tied to a specific `pointerId` and not related to a specific pointer location. For example, if a touch-drag causes scroll (and therefore the firing of a `pointercancel` event), the user agent absorbs the last `pointermove` events to determine the scroll amount etc and the page is not expected to know those event locations. Developers can cache the last `pointermove` for that `pointerId` if there is any use. We have a [Chrome bug](https://bugs.chromium.org/p/chromium/issues/detail?id=724013) about it which we are planning to close soon. Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/463 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 December 2022 17:30:13 UTC