Pointer Events WG call

Past

Confirmed

Meeting

Event details

Date:: 7 July 2021, 11:00–12:00 Eastern Daylight Time
Status:: Confirmed
Repeats:: Every other week on Wednesday, starting from 31 March 2021, until 08 December 2021; Overview of the recurring event
Groups:: Pointer Events Working Group ( View calendar)

Regular fortnightly call

Pull requests:

Review 'Update targets of predicted and coalesced events when trusted event target changes.' https://github.com/w3c/pointerevents/pull/390
Review 'Expand explanation for non-coalesced events' https://github.com/w3c/pointerevents/pull/379 (in particular, use of "measurable" in the definition)
Review 'Simplify/clarify coalesced and predicted events' https://github.com/w3c/pointerevents/pull/377 (note that @Flackr wanted to add to this https://www.w3.org/2021/05/26-pointerevents-minutes.html#a01 - if you could find the time to do this before the call, that'd be awesome)

Issues related to coalesced/predicted events that need clarification (checking status on these):

Unclear note about PointerEvent initialization of attributes to reflect coalesced events https://github.com/w3c/pointerevents/issues/374
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

Other issues:

HTML monkeypatching: initiate the drag-and-drop operation definition https://github.com/w3c/pointerevents/issues/384

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

Please log in to export this event with all the information you have access to.

The following links do not contain any sensitive information and can be shared publicly.

Report feedback and issues on GitHub.