Event Updated: Pointer Events WG call

[View this event in your browser](https://www.w3.org/events/meetings/9718517d-0e08-4377-bb7c-07332948233b/20211208T110000)

 Pointer Events WG call Upcoming Confirmed
==========================================

 08 December 2021, 11:00 -12:00 America/New\_York

 Event is recurring every other week on Wednesday, starting from 2021-03-31, until 2021-12-08

[ Pointer Events Working Group ](https://www.w3.org/groups/wg/pointer-events/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
------

[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)Quick round-up of PRs merged since last meeting:

- Remove should from boundary events note and move to normative must <https://github.com/w3c/pointerevents/pull/419>
- Reword altitudeAngle note, expand tiltX and tiltY explanation <https://github.com/w3c/pointerevents/pull/422>
- Improve illustrations <https://github.com/w3c/pointerevents/pull/423>

Issues:

- How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit <https://github.com/w3c/pointerevents/issues/223>
  Action from last meeting: Olli to look at remaining constructor work for #223
- touch-action:none and overflow:auto <https://github.com/w3c/pointerevents/issues/319>
  Action from last meeting: review #319 for next meeting and see then if we can/should add extra wording to spec for this
- three open issues around pointer capture (make sense to look at these in block?)
  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>

All outstanding v3 issues: <https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aopen+label%3Av3>

Minutes from last meeting <https://www.w3.org/2021/11/10-pointerevents-minutes.html>

 Joining Instructions
--------------------

 Instructions are restricted to meeting participants. You need to [ log in](/accounts/login?redirect_url=/events/meetings/9718517d-0e08-4377-bb7c-07332948233b/20211208T110000/edit) to see them.

 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))

 Report feedback and issues on [ GitHub](https://github.com/w3c/calendar "W3C Calendar GitHub repository").