public-pointer-events@w3.org from January to March 2020 by author

Daniel Libby via GitHub

Re: [pointerevents] Consider a simple API for low-latency pointer trails (#204) (Wednesday, 12 February)

Domenic Denicola via GitHub

Re: [pointerevents] Add secure context criteria to pointerrawupdate and getCoalescedEvents (#318) (Thursday, 19 March)
Re: [pointerevents] Add secure context criteria to pointerrawupdate and getCoalescedEvents (#318) (Thursday, 19 March)

Liviu Tinta via GitHub

Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Tuesday, 31 March)

Navid Zolghadr

Re: PEWG call this week (1 April)? (Monday, 30 March)
Re: Potential Pointer Events WG call 22 January 2020 (Wednesday, 22 January)
Re: Potential Pointer Events WG call 22 January 2020 (Wednesday, 22 January)

Navid Zolghadr via GitHub

Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Monday, 30 March)
Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Monday, 30 March)
Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Thursday, 26 March)
Re: [pointerevents] Add secure context criteria to pointerrawupdate and getCoalescedEvents (#318) (Thursday, 19 March)
Re: [pointerevents] Add secure context criteria to pointerrawupdate and getCoalescedEvents (#318) (Thursday, 19 March)
[pointerevents] Pull Request: Add secure context criteria to pointerrawupdate and getCoalescedEvents (Thursday, 19 March)
[pointerevents] Pull Request: Change the type of click, auxclick, and contextmenu to PointerEvent (Monday, 9 March)

Patrick H. Lauke

Pointer Events WG call 1 April 2020 (Tuesday, 31 March)
PEWG call this week (1 April)? (Monday, 30 March)
*NO* Pointer Events WG call 4 March 2020 (Wednesday, 4 March)
PEP help, if anybody has time/inclination (Wednesday, 19 February)
Minutes from Pointer Events WG call 19 Feb 2020 (Wednesday, 19 February)
Re: Pointer Events WG call 19 Feb 2020 (Wednesday, 19 February)
Pointer Events WG call 19 Feb 2020 (Wednesday, 19 February)
WICG topic/request concerning PE (Tuesday, 18 February)
Re: [pointerevents] Pull Request: add altitudeAngle/azimuthAngle (Monday, 17 February)
Minutes from Pointer Events WG call today 5 Feb 2020 (Wednesday, 5 February)
Pointer Events WG call today 5 Feb 2020 (Wednesday, 5 February)
Re: Potential Pointer Events WG call 22 January 2020 (Wednesday, 22 January)
Potential Pointer Events WG call 22 January 2020 (Tuesday, 21 January)

Patrick H. Lauke via GitHub

Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Monday, 30 March)
Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Monday, 30 March)
Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Thursday, 26 March)
Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Thursday, 26 March)
Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Wednesday, 18 March)
Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Wednesday, 18 March)
Re: [pointerevents] add altitudeAngle/azimuthAngle (#316) (Wednesday, 18 March)
Closed: [pointerevents] Consider a simple API for low-latency pointer trails (#204) (Wednesday, 19 February)
Re: [pointerevents] Consider a simple API for low-latency pointer trails (#204) (Wednesday, 19 February)
Re: [pointerevents] How best to inflate hit targets for touch? (#126) (Wednesday, 19 February)
Re: [pointerevents] Define event order relative to RAF? (#9) (Wednesday, 19 February)
Re: [pointerevents] tiltX and tiltY aren't as helpful as just having altitude angle (#274) (Wednesday, 19 February)
[pointerevents] Pull Request: add altitudeAngle/azimuthAngle (Monday, 17 February)
[pointerevents] new commits pushed by patrickhlauke (Wednesday, 5 February)

Philippe Le Hegaret via GitHub

[pointerevents] Pull Request: Various README updates (Wednesday, 5 February)

Philippe Le Hégaret

Auto-managed GitHub teams (Wednesday, 12 February)

smaug---- via GitHub

Re: [pointerevents] Consider a simple API for low-latency pointer trails (#204) (Wednesday, 19 February)
Re: [pointerevents] How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit (#223) (Wednesday, 19 February)
Re: [pointerevents] Should getCoalescedEvents() return always the same objects or new instances with same data? (#227) (Wednesday, 19 February)
Re: [pointerevents] Limit pointerrawupdate and getCoalescedEvents API to secure origins (#277) (Wednesday, 19 February)

sysbot+ipp@w3.org

[Reminder] Call for Exclusions: Pointer Events Level 3 (Thursday, 12 March)

Last message date: Tuesday, 31 March 2020 17:27:17 UTC