BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20210527T141121Z
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:20210527T141121Z
SUMMARY:Pointer Events WG call
DTSTART;TZID=America/New_York:20210526T110000
DTEND;TZID=America/New_York:20210526T120000
DESCRIPTION:https://www.w3.org/events/meetings/9718517d-0e08-4377-bb7c-0733
 2948233b/20210526T110000/\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\n* Review 'Simplify/clarify coalesced and pr
 edicted events' https://github.com/w3c/pointerevents/pull/377\n\nIssues re
 lated to coalesced/predicted events that need clarification:\n\n* Do user 
 agents only coalesce pointermove events relating to changes in position? h
 ttps://github.com/w3c/pointerevents/issues/375\n* Unclear note about Point
 erEvent initialization of attributes to reflect coalesced events https://g
 ithub.com/w3c/pointerevents/issues/374\n* It is unclear how predicted even
 ts' timestamps should relate to actual dispatched events https://github.co
 m/w3c/pointerevents/issues/282\n* The behavior of getCoalescedEvent in poi
 nterevent_constructor.html is inconsistent with the spec https://github.co
 m/w3c/pointerevents/issues/229\n* "This API always returns at least one co
 alesced event for pointermove events and an empty list for other types of 
 PointerEvents." https://github.com/w3c/pointerevents/issues/224\n* How is 
 pointer event ctor supposed to work when coalescedEvents is passed using t
 he PointerEventInit https://github.com/w3c/pointerevents/issues/223\n\nTri
 age: can these issues be closed?\n\n* Clarify whether touch contact must f
 ire a pointerrawupdate event https://github.com/w3c/pointerevents/issues/3
 73\n* Immediately firing coalesced events for enter/leave/over/out? https:
 //github.com/w3c/pointerevents/issues/278\n\nNote all v3 marked issues sti
 ll pending https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Ao
 pen+label%3Av3\n\nSee minutes from last call 12 May 2021 https://www.w3.or
 g/2021/05/12-pointerevents-minutes.html\n\nNote that since that call\, the
  following PR was merged https://github.com/w3c/pointerevents/pull/376
STATUS:CONFIRMED
CREATED:20210523T110611Z
LAST-MODIFIED:20210527T141121Z
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:20210526T110000
END:VEVENT
END:VCALENDAR