[webkit-dev] Request for position on changing click, auxclick, contextmenu to PointerEvent
liviutinta at chromium.org
Fri Nov 6 10:38:32 PST 2020
I'd like to ask for Webkit's official position on changing “click”,
“contextmenu”, “auxclick” events to PointerEvent (instead of MouseEvent) to
- distinguish between mouse, pen and individual fingers in a multitouch
interaction through pointerType and pointerId attributes, and
- utilize fractional event coordinates for high precision use cases
There were concerns about compat implications of this change but our compat
study (see below) does not support those concerns.
The "click" and "contextmenu" events were defined as MouseEvents decades
ago when a mouse was the only source of pointer-like events. The "auxclick"
event was defined similarly only a few years ago. The ability to
distinguish these events by input source in a multi-pointer environment is
a long-standing developer request (e.g. this MSDN request ).
PointerEvents spec discussion  reached consensus that it would be a
useful change and also expressed compat concerns .
To better understand compat implications, Chrome committed  to
experimenting in the wild. Chrome made the change available as an
experimental web-platform feature in Sep 2019, started an experiment in
Canary in Aug 2020, and gradually expanded the scope of the experiment to
cover Canary, Dev and Beta by Nov 3rd 2020. So far there were no related
Related specification changes:
PointerEvents pending PR 
UIEvents merged PR 
Html pending PR1 
Html pending PR2 
TAG Review: <https://github.com/w3ctag/design-reviews/issues/537>The TAG
review process is being skipped because this change does not involve a
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev