Event Updated: Pointer Events WG call

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

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

 18 August 2021, 11:00 -12:00

 Event is recurring every other week on Wednesday, starting from 2021-03-31, until 2022-01-05

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

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

 Instructions are restricted to meeting participants. You need to [ log in](/accounts/login?redirect_url=/events/meetings/9718517d-0e08-4377-bb7c-07332948233b/20210818T110000/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").