Pointer Events WG call
- Past
- Confirmed
- Past
- Confirmed
Meeting
Regular fortnightly call
Agenda
Pull requests:
-
Expand note about preventing compatibility mouse events https://github.com/w3c/pointerevents/pull/403
see additional comment here after our call two weeks ago https://github.com/w3c/pointerevents/pull/403#issuecomment-892968317 -
Add note about rounding coordinates for click, auxclick, contextmenu https://github.com/w3c/pointerevents/pull/404
the fact that normatively PE don't say that coordinates should be double (currently only makes a non-normative reference to the CSSOM extension) is leading to a lot of ifs and buts. wonder if instead PE should/can just say that they must be double?
Open v3 issues to discuss (see how many we can get through):
-
Notes with normative (SHOULD/MUST) statements https://github.com/w3c/pointerevents/issues/405
-
Clarify which steps constitute canceling a pointer https://github.com/w3c/pointerevents/issues/400
-
How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit https://github.com/w3c/pointerevents/issues/223
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers https://github.com/w3c/pointerevents/issues/285
-
touch-action:none and overflow:auto https://github.com/w3c/pointerevents/issues/319
-
Order of pointer events across frames when using pointer capture https://github.com/w3c/pointerevents/issues/355
-
Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356
-
Clarify when lostpointercapture should fire https://github.com/w3c/pointerevents/issues/357
-
Clarify which steps constitute canceling a pointer https://github.com/w3c/pointerevents/issues/400
Minutes from last meeting https://www.w3.org/2021/08/04-pointerevents-minutes.html
Minutes
Read minutesExport options
Personal Links
Please log in to export this event with all the information you have access to.
Public Links
The following links do not contain any sensitive information and can be shared publicly.