public-pointer-events@w3.org from April to June 2021 by author

Anne van Kesteren via GitHub

• Re: [pointerevents] How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit (#223) (Monday, 17 May)
• Re: [pointerevents] How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit (#223) (Monday, 17 May)

chaals via GitHub

• Re: [pointerevents] Move glossary to the end of the spec (#362) (Sunday, 18 April)

Edgar Chen via GitHub

• Re: [pointerevents] Clarify when lostpointercapture should fire (#357) (Wednesday, 14 April)

Fuqiao Xue via GitHub

• Re: [pointerevents] [css-touch-action] disable webview swipe back behavior (#358) (Sunday, 4 April)

Gary Kacmarcik via GitHub

• Re: [pointerevents] Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers (#285) (Tuesday, 4 May)

Joe Pea via GitHub

• Re: [pointerevents] `touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. (#387) (Friday, 18 June)
• [pointerevents] `touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. (#387) (Friday, 18 June)
• Re: [pointerevents] `touch-action: none` definition is too vague (#276) (Friday, 18 June)

Liam DeBeasi via GitHub

• Re: [pointerevents] touch-action: disable webview swipe back behavior (#358) (Tuesday, 13 April)

Lincoln Baxter, III via GitHub

• Re: [pointerevents] touch-action: disable webview swipe back behavior (#358) (Tuesday, 13 April)
• Re: [pointerevents] touch-action: disable webview swipe back behavior (#358) (Tuesday, 13 April)
• Re: [pointerevents] touch-action: disable webview swipe back behavior (#358) (Tuesday, 13 April)

Marcos Cáceres via GitHub

• Re: [pointerevents] Refreshing references using latest respec magic (#381) (Thursday, 10 June)
• Re: [pointerevents] Refreshing references using latest respec magic (#381) (Saturday, 29 May)

Mark Salsbery via GitHub

• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Wednesday, 21 April)

Mustaq Ahmed via GitHub

• Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356) (Thursday, 17 June)
• Re: [pointerevents] Add figures for altitudeAngle and azimuthAngle (#378) (Tuesday, 18 May)
• Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356) (Wednesday, 5 May)
• Re: [pointerevents] Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers (#285) (Tuesday, 4 May)
• Re: [pointerevents] Move Navid Zoghadr to former editors (#371) (Monday, 3 May)
• Re: [pointerevents] disambiguate default *action* and default *behavior* in prose (#368) (Tuesday, 27 April)
• Re: [pointerevents] Add note explicitly about mouse compat events, preventDefault, and passive events (#369) (Tuesday, 27 April)
• Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Thursday, 22 April)
• Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Wednesday, 21 April)
• Re: [pointerevents] Add new section explaining coalesced and predicted events (#364) (Wednesday, 21 April)
• Re: [pointerevents] Should "click", "dblclick" and "contextmenu" events be PointerEvents? (#100) (Tuesday, 13 April)

Navid Zolghadr via GitHub

• Re: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380) (Wednesday, 2 June)
• Re: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380) (Monday, 31 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Wednesday, 12 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Tuesday, 11 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Tuesday, 11 May)
• Re: [pointerevents] Move Navid Zoghadr to former editors (#371) (Monday, 3 May)
• Re: [pointerevents] Move Navid Zoghadr to former editors (#371) (Saturday, 1 May)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Wednesday, 21 April)
• Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Wednesday, 21 April)
• Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Wednesday, 21 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Tuesday, 20 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Wednesday, 14 April)
• Re: [pointerevents] touch-action: disable webview swipe back behavior (#358) (Tuesday, 13 April)

Nirjhar Vermani via GitHub

• Re: [pointerevents] touch-action: disable webview swipe back behavior (#358) (Friday, 28 May)

Patrick H. Lauke

• Minutes from Pointer Events WG call 23 June 2021 (Wednesday, 23 June)
• Cancelling upcoming PEWG meeting 9 June 2021 (Sunday, 6 June)
• Weird events sequence/behaviour in Chrome/iOS (Friday, 4 June)
• Minutes from Pointer Events WG call 26 May 2021 (Wednesday, 26 May)
• Re: Event Invitation: Pointer Events WG call (Wednesday, 26 May)
• Minutes from Pointer Events WG call 12 May 2021 (Wednesday, 12 May)
• Re: Minutes from Pointer Events WG call 28 April 2021 (Monday, 10 May)
• (belated) Minutes from Pointer Events WG call 14 April 2021 (Wednesday, 28 April)
• Minutes from Pointer Events WG call 28 April 2021 (Wednesday, 28 April)

Patrick H. Lauke via GitHub

• [pointerevents] new commits pushed by patrickhlauke (Wednesday, 30 June)
• Closed: [pointerevents] HTML monkeypatching: animation frame callbacks (#385) (Wednesday, 30 June)
• Re: [pointerevents] Remove mention of animation frame callback (#388) (Wednesday, 23 June)
• [pointerevents] new commits pushed by patrickhlauke (Wednesday, 23 June)
• Re: [pointerevents] Remove mention of animation frame callback (#388) (Wednesday, 23 June)
• [pointerevents] Pull Request: Remove mention of animation frame callback (Wednesday, 23 June)
• [pointerevents] new commits pushed by patrickhlauke (Wednesday, 23 June)
• Re: [pointerevents] `touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. (#387) (Friday, 18 June)
• Re: [pointerevents] `touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. (#387) (Friday, 18 June)
• [pointerevents] new commits pushed by patrickhlauke (Monday, 14 June)
• [pointerevents] new commits pushed by patrickhlauke (Monday, 14 June)
• Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377) (Monday, 14 June)
• Re: [pointerevents] Expand explanation for non-coalesced events (#379) (Thursday, 10 June)
• Re: [pointerevents] Refreshing references using latest respec magic (#381) (Thursday, 10 June)
• Re: [pointerevents] Refreshing references using latest respec magic (#381) (Thursday, 10 June)
• Closed: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380) (Thursday, 10 June)
• [pointerevents] new commits pushed by patrickhlauke (Thursday, 10 June)
• Closed: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282) (Thursday, 10 June)
• [pointerevents] new commits pushed by patrickhlauke (Thursday, 10 June)
• [pointerevents] Pull Request: Explicit note about pointerrawmove having an empty predicted event list (Wednesday, 2 June)
• Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377) (Wednesday, 2 June)
• Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375) (Wednesday, 2 June)
• [pointerevents] Pull Request: Expand the definition/explanation of predicted events timestamps (Wednesday, 2 June)
• Re: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380) (Tuesday, 1 June)
• Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375) (Wednesday, 26 May)
• Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375) (Wednesday, 26 May)
• Re: [pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374) (Wednesday, 26 May)
• Re: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380) (Sunday, 23 May)
• [pointerevents] do `pointerrawupdate` events also get predicted events? (#380) (Sunday, 23 May)
• [pointerevents] Pull Request: Expand explanation for non-coalesced events (Sunday, 23 May)
• Re: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282) (Saturday, 22 May)
• Re: [pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374) (Saturday, 22 May)
• Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377) (Saturday, 22 May)
• Closed: [pointerevents] disambiguate default *action* and default *behavior* in prose (#368) (Saturday, 22 May)
• [pointerevents] new commits pushed by patrickhlauke (Saturday, 22 May)
• Closed: [pointerevents] Clarify/expand introduction to the touch-action section (#366) (Saturday, 22 May)
• Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377) (Wednesday, 19 May)
• Re: [pointerevents] Add figures for altitudeAngle and azimuthAngle (#378) (Wednesday, 19 May)
• Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377) (Monday, 17 May)
• Re: [pointerevents] Clarify the coalesced/predicted targets dirty stuff, and clarify better how these events are generated/populated and when (#370) (Monday, 17 May)
• [pointerevents] new commits pushed by patrickhlauke (Sunday, 16 May)
• [pointerevents] new commits pushed by patrickhlauke (Sunday, 16 May)
• [pointerevents] new commits pushed by patrickhlauke (Sunday, 16 May)
• [pointerevents] new commits pushed by patrickhlauke (Sunday, 16 May)
• Re: [pointerevents] Add figures for altitudeAngle and azimuthAngle (#378) (Sunday, 16 May)
• [pointerevents] Pull Request: Add figures for altitudeAngle and azimuthAngle (Sunday, 16 May)
• [pointerevents] Pull Request: Simplify/clarify coalesced and predicted events (Saturday, 15 May)
• Re: [pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370) (Saturday, 15 May)
• Re: [pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370) (Saturday, 15 May)
• Re: [pointerevents] Should "click", "dblclick" and "contextmenu" events be PointerEvents? (#100) (Saturday, 15 May)
• [pointerevents] Pull Request: Clarify the rationale and purpose of touch-action (Saturday, 15 May)
• [pointerevents] new commits pushed by patrickhlauke (Saturday, 15 May)
• [pointerevents] new commits pushed by patrickhlauke (Saturday, 15 May)
• [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375) (Thursday, 13 May)
• Closed: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361) (Thursday, 13 May)
• [pointerevents] new commits pushed by patrickhlauke (Thursday, 13 May)
• Re: [pointerevents] Add new section explaining coalesced and predicted events (#364) (Thursday, 13 May)
• [pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374) (Thursday, 13 May)
• [pointerevents] new commits pushed by patrickhlauke (Wednesday, 12 May)
• Closed: [pointerevents] Normatively make touch-action apply for direct-manipulation pen devices (#202) (Wednesday, 12 May)
• Re: [pointerevents] "This API always returns at least one coalesced event for pointermove events and an empty list for other types of PointerEvents." (#224) (Wednesday, 12 May)
• Re: [pointerevents] Should events queue a task? (#197) (Wednesday, 12 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Wednesday, 12 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Tuesday, 11 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Tuesday, 11 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Tuesday, 11 May)
• [pointerevents] new commits pushed by patrickhlauke (Monday, 3 May)
• Re: [pointerevents] Move Navid Zoghadr to former editors (#371) (Monday, 3 May)
• Re: [pointerevents] Move Navid Zoghadr to former editors (#371) (Monday, 3 May)
• Re: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282) (Sunday, 2 May)
• Re: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282) (Sunday, 2 May)
• Re: [pointerevents] Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers (#285) (Sunday, 2 May)
• Re: [pointerevents] Add new section explaining coalesced and predicted events (#364) (Sunday, 2 May)
• Re: [pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370) (Sunday, 2 May)
• Re: [pointerevents] Move Navid Zoghadr to former editors (#371) (Saturday, 1 May)
• [pointerevents] Pull Request: Update WCAG keyboard reference to latest spec version (Friday, 30 April)
• Re: [pointerevents] Move Navid Zoghadr to former editors (#371) (Friday, 30 April)
• [pointerevents] Pull Request: Move Navid Zoghadr to former editors (Friday, 30 April)
• Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350) (Wednesday, 28 April)
• Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350) (Wednesday, 28 April)
• Re: [pointerevents] disambiguate default *action* and default *behavior* in prose (#368) (Tuesday, 27 April)
• Re: [pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370) (Tuesday, 27 April)
• [pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370) (Tuesday, 27 April)
• Re: [pointerevents] Add new section explaining coalesced and predicted events (#364) (Saturday, 24 April)
• Re: [pointerevents] Add new section explaining coalesced and predicted events (#364) (Saturday, 24 April)
• Re: [pointerevents] Add new section explaining coalesced and predicted events (#364) (Thursday, 22 April)
• Re: [pointerevents] Add new section explaining coalesced and predicted events (#364) (Thursday, 22 April)
• Closed: [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Thursday, 22 April)
• [pointerevents] Add note explicitly about mouse compat events, preventDefault, and passive events (#369) (Thursday, 22 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Thursday, 22 April)
• Closed: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Thursday, 22 April)
• [pointerevents] disambiguate default *action* and default *behavior* in prose (#368) (Thursday, 22 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Thursday, 22 April)
• Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Wednesday, 21 April)
• Closed: [pointerevents] Move glossary to the end of the spec (#362) (Wednesday, 21 April)
• [pointerevents] new commits pushed by patrickhlauke (Wednesday, 21 April)
• Re: [pointerevents] Move glossary to the end of the spec (#363) (Wednesday, 21 April)
• [pointerevents] new commits pushed by patrickhlauke (Tuesday, 20 April)
• [pointerevents] Pull Request: Update readme (Tuesday, 20 April)
• [pointerevents] new commits pushed by patrickhlauke (Tuesday, 20 April)
• Re: [pointerevents] Improve legibility/style of pointerrawupdate section (#365) (Tuesday, 20 April)
• Re: [pointerevents] Move glossary to the end of the spec (#362) (Tuesday, 20 April)
• Re: [pointerevents] Move glossary to the end of the spec (#363) (Tuesday, 20 April)
• Re: [pointerevents] Add new section explaining coalesced and predicted events (#364) (Tuesday, 20 April)
• Re: [pointerevents] Improve legibility/style of pointerrawupdate section (#365) (Tuesday, 20 April)
• Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Tuesday, 20 April)
• [pointerevents] Clarify/expand introduction to the touch-action section (#366) (Sunday, 18 April)
• Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Sunday, 18 April)
• Re: [pointerevents] Improve legibility/style of pointerrawupdate section (#365) (Sunday, 18 April)
• [pointerevents] Pull Request: Improve legibility/style of pointerrawupdate section (Sunday, 18 April)
• Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361) (Sunday, 18 April)
• [pointerevents] Pull Request: Add new section explaining coalesced and predicted events (Sunday, 18 April)
• Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361) (Saturday, 17 April)
• [pointerevents] Pull Request: Move glossary to the end of the spec (Saturday, 17 April)
• Re: [pointerevents] Move glossary to the end of the spec (#362) (Saturday, 17 April)
• [pointerevents] Move glossary to the end of the spec (#362) (Saturday, 17 April)
• Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361) (Saturday, 17 April)
• Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361) (Saturday, 17 April)
• Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361) (Friday, 16 April)
• Closed: [pointerevents] Specify exactly how event coalescing works (#328) (Friday, 16 April)
• Re: [pointerevents] Specify exactly how event coalescing works (#328) (Friday, 16 April)
• Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361) (Friday, 16 April)
• Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361) (Friday, 16 April)
• [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361) (Friday, 16 April)
• [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Wednesday, 14 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Wednesday, 14 April)
• Re: [pointerevents] Clarify when lostpointercapture should fire (#357) (Wednesday, 14 April)
• Closed: [pointerevents] Click event while a pointer event is captured (#75) (Wednesday, 14 April)
• Re: [pointerevents] Click event while a pointer event is captured (#75) (Wednesday, 14 April)
• Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350) (Wednesday, 7 April)
• Closed: [pointerevents] `touch-action: none` definition is too vague (#276) (Wednesday, 7 April)
• [pointerevents] new commits pushed by patrickhlauke (Wednesday, 7 April)
• Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350) (Saturday, 3 April)
• Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356) (Thursday, 1 April)

Philippe Le Hegaret via GitHub

• Re: [pointerevents] Remove mention of animation frame callback (#388) (Wednesday, 23 June)
• [pointerevents] Pull Request: More minor tweaks (Wednesday, 23 June)
• [pointerevents] Pull Request: task queue is not reliable HTML concept. Use event loop instead (Thursday, 10 June)
• [pointerevents] HTML monkeypatching: animation frame callbacks (#385) (Thursday, 10 June)
• [pointerevents] HTML monkeypatching: initiate the drag-and-drop operation definition (#384) (Thursday, 10 June)
• [pointerevents] new commits pushed by plehegar (Thursday, 10 June)
• [pointerevents] new commits pushed by plehegar (Wednesday, 2 June)
• [pointerevents] Pull Request: Refreshing references using latest respec magic (Thursday, 27 May)
• [pointerevents] new commits pushed by plehegar (Wednesday, 19 May)
• [pointerevents] new commits pushed by plehegar (Wednesday, 12 May)
• [pointerevents] new commits pushed by plehegar (Wednesday, 12 May)

Robert Flack via GitHub

• Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375) (Wednesday, 26 May)
• Re: [pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374) (Wednesday, 26 May)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Thursday, 22 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Wednesday, 21 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Tuesday, 20 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Thursday, 15 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Thursday, 15 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Wednesday, 14 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Wednesday, 14 April)
• [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Wednesday, 14 April)
• Re: [pointerevents] Enable direct pen and touch to have different touch-action behavior (#203) (Wednesday, 14 April)
• Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356) (Wednesday, 14 April)

smaug---- via GitHub

• Re: [pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374) (Wednesday, 26 May)
• Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375) (Wednesday, 26 May)
• Re: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282) (Wednesday, 26 May)
• Re: [pointerevents] "This API always returns at least one coalesced event for pointermove events and an empty list for other types of PointerEvents." (#224) (Wednesday, 12 May)
• Re: [pointerevents] How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit (#223) (Wednesday, 12 May)
• Re: [pointerevents] How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit (#223) (Wednesday, 12 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Wednesday, 12 May)
• Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356) (Wednesday, 28 April)
• Re: [pointerevents] Move glossary to the end of the spec (#362) (Wednesday, 21 April)
• Re: [pointerevents] Move glossary to the end of the spec (#363) (Tuesday, 20 April)
• Re: [pointerevents] Move glossary to the end of the spec (#362) (Tuesday, 20 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Tuesday, 20 April)
• Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360) (Tuesday, 20 April)
• Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359) (Wednesday, 14 April)

W3C Calendar

• Event Invitation: Pointer Events WG call (Tuesday, 22 June)
• Event Cancelled: "Pointer Events WG call" (Wednesday, 9 June)
• Event Invitation: Pointer Events WG call (Sunday, 6 June)
• Event Invitation: Pointer Events WG call (Sunday, 6 June)
• Event Invitation: Pointer Events WG call (Sunday, 6 June)
• Event Invitation: Pointer Events WG call (Sunday, 6 June)
• Event Invitation: Pointer Events WG call (Sunday, 23 May)
• Event Invitation: Pointer Events WG call (Monday, 10 May)
• Event Invitation: Pointer Events WG call (Tuesday, 27 April)
• Event Invitation: Pointer Events WG call (Tuesday, 13 April)

Yacine Hmito via GitHub

• Re: [pointerevents] Proposal: a way of tracking pointer position on pan/zoom touch-action (#339) (Wednesday, 12 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Wednesday, 12 May)
• Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Sunday, 9 May)
• [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373) (Sunday, 9 May)

Last message date: Wednesday, 30 June 2021 19:20:30 UTC