Pointer Events WG call
- Past
- Confirmed
- Past
- Confirmed
Meeting
Regular fortnightly call
Agenda
- Review 'Simplify/clarify coalesced and predicted events' https://github.com/w3c/pointerevents/pull/377
Issues related to coalesced/predicted events that need clarification:
- Do user agents only coalesce pointermove events relating to changes in position? https://github.com/w3c/pointerevents/issues/375
- Unclear note about PointerEvent initialization of attributes to reflect coalesced events https://github.com/w3c/pointerevents/issues/374
- It is unclear how predicted events' timestamps should relate to actual dispatched events https://github.com/w3c/pointerevents/issues/282
- The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec https://github.com/w3c/pointerevents/issues/229
- "This API always returns at least one coalesced event for pointermove events and an empty list for other types of PointerEvents." https://github.com/w3c/pointerevents/issues/224
- How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit https://github.com/w3c/pointerevents/issues/223
Triage: can these issues be closed?
- Clarify whether touch contact must fire a pointerrawupdate event https://github.com/w3c/pointerevents/issues/373
- Immediately firing coalesced events for enter/leave/over/out? https://github.com/w3c/pointerevents/issues/278
Note all v3 marked issues still pending https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aopen+label%3Av3
See minutes from last call 12 May 2021 https://www.w3.org/2021/05/12-pointerevents-minutes.html
Note that since that call, the following PR was merged https://github.com/w3c/pointerevents/pull/376
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.