BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20210817T234124Z
BEGIN:VTIMEZONE
TZID:America/New_York
X-MICROSOFT-CDO-TZID:10
BEGIN:STANDARD
DTSTART:20201101T060000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:STANDARD
DTSTART:20211107T060000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20210314T070000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:9718517d-0e08-4377-bb7c-07332948233b
DTSTAMP:20210817T234124Z
SUMMARY:Pointer Events WG call
DTSTART;TZID=America/New_York:20210818T110000
DTEND;TZID=America/New_York:20210818T120000
DESCRIPTION:https://www.w3.org/events/meetings/9718517d-0e08-4377-bb7c-0733
 2948233b/20210818T110000/\n\nRegular fortnightly call \n\n* [Issues](https
 ://github.com/w3c/pointerevents/issues)\n* [Pull Requests](https://github.
 com/w3c/pointerevents/pulls)\n* [Draft](https://w3c.github.io/pointerevent
 s/)\n* [Mailing list](https://lists.w3.org/Archives/Public/public-pointer-
 events/)\n\nAgenda: https://www.w3.org/Search/Mail/Public/search?keywords=
 &hdr-1-name=subject&hdr-1-query=%22WG+Call%22&index-type=t&type-index=publ
 ic-pointer-events\n\nAgenda\n\nPull requests:\n\n* Expand note about preve
 nting compatibility mouse events https://github.com/w3c/pointerevents/pull
 /403\nsee additional comment here after our call two weeks ago https://git
 hub.com/w3c/pointerevents/pull/403#issuecomment-892968317\n\n* Add note ab
 out rounding coordinates for click\, auxclick\, contextmenu https://github
 .com/w3c/pointerevents/pull/404\nthe fact that normatively PE don't say th
 at coordinates should be double (currently only makes a non-normative refe
 rence 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?\n\n\nOpen v3 i
 ssues to discuss (see how many we can get through):\n\n* Notes with normat
 ive (SHOULD/MUST) statements https://github.com/w3c/pointerevents/issues/4
 05\n\n* Clarify which steps constitute canceling a pointer https://github.
 com/w3c/pointerevents/issues/400\n\n* How is pointer event ctor supposed t
 o work when coalescedEvents is passed using the PointerEventInit https://g
 ithub.com/w3c/pointerevents/issues/223\n\n* Changing the DOM hierarchy whi
 le handling a "pointerenter" event produces significantly different result
 s across browsers https://github.com/w3c/pointerevents/issues/285\n\n* tou
 ch-action:none and overflow:auto https://github.com/w3c/pointerevents/issu
 es/319\n\n* Order of pointer events across frames when using pointer captu
 re https://github.com/w3c/pointerevents/issues/355\n\n* Clarify what the t
 arget of the click event should be after capturing pointer events https://
 github.com/w3c/pointerevents/issues/356\n\n* Clarify when lostpointercaptu
 re should fire https://github.com/w3c/pointerevents/issues/357\n\n* Clarif
 y which steps constitute canceling a pointer https://github.com/w3c/pointe
 revents/issues/400\n\n\nMinutes from last meeting https://www.w3.org/2021/
 08/04-pointerevents-minutes.html
STATUS:CONFIRMED
CREATED:20210817T234123Z
LAST-MODIFIED:20210817T234124Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Pointer Events Wor
 king Group:mailto:public-pointer-events@w3.org
RECURRENCE-ID;TZID=America/New_York:20210818T110000
END:VEVENT
END:VCALENDAR