- From: W3C Calendar <noreply@w3.org>
- Date: Sun, 23 May 2021 11:06:13 +0000
- To: Pointer Events Working Group <public-pointer-events@w3.org>
- Message-ID: <7f3c17921e78443efac7f0818328c405@w3.org>
[View this event in your browser](https://www.w3.org/events/meetings/9718517d-0e08-4377-bb7c-07332948233b/20210526T110000) Pointer Events WG call Confirmed ================================== 26 May 2021, 11:00 - 12:00 America/New_York [ Pointer Events Working Group ](https://www.w3.org/groups/wg/pointer-events/calendar "Pointer Events Working Group Calendar") Regular fortnightly call - [Issues](https://github.com/w3c/pointerevents/issues) - [Pull Requests](https://github.com/w3c/pointerevents/pulls) - [Draft](https://w3c.github.io/pointerevents/) - [Mailing list](https://lists.w3.org/Archives/Public/public-pointer-events/) - - - - - - 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> Joining Instructions -------------------- Instructions are restricted to meeting participants. - - - - - - Participants ------------ ### Groups - [Pointer Events Working Group](https://www.w3.org/groups/wg/pointer-events) ([ View Calendar](https://www.w3.org/groups/wg/pointer-events/calendar)) - - - - - - [ Agenda ](https://www.w3.org/Search/Mail/Public/search?keywords=&hdr-1-name=subject&hdr-1-query=%22WG+Call%22&index-type=t&type-index=public-pointer-events)
Attachments
- text/calendar attachment: event.ics
Received on Sunday, 23 May 2021 11:06:15 UTC