[pointerevents] Inconsistent ordering of `pointerleave` events during touch interactions (#431)

dfreedm has just created a new issue for https://github.com/w3c/pointerevents:

== Inconsistent ordering of `pointerleave` events during touch interactions ==
The [pointerup](https://www.w3.org/TR/pointerevents/#the-pointerup-event), [pointercancel](https://www.w3.org/TR/pointerevents/#the-pointercancel-event), and [pointerleave](https://www.w3.org/TR/pointerevents/#the-pointerleave-event) events all specify that `pointerleave` must be sent after `pointerup` or `pointercancel` for interactions that do not support hovering.
However, multiple vendors (Chromium and Firefox at least) are dispatching `pointerleave` immediately after `pointerup`, and before `click`, which is incompatible with the [mapping for devices that do not support hover](https://www.w3.org/TR/pointerevents/#mapping-for-devices-that-do-not-support-hover).

Example: 
![Screen Shot 2022-02-07 at 10 58 03 AM](https://user-images.githubusercontent.com/46725/152853630-fee41a32-0b3b-46bb-b76a-73d5bea533b4.png)
https://marred-traveling-crustacean.glitch.me/

Is the suggested mapping in the spec supposed to be a normative mapping, or should it reflect what vendors have implemented?

Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/431 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 7 February 2022 19:00:20 UTC