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

Dan Burzo via GitHub

• Re: [pointerevents] touch-action - incorrect values in note for pull-to-refresh? (#41) (Wednesday, 20 January)
• Re: [pointerevents] touch-action - incorrect values in note for pull-to-refresh? (#41) (Wednesday, 20 January)

Joe Pea via GitHub

• Re: [pointerevents] Extend pointer events to support raw trackpad data (#206) (Monday, 1 February)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Sunday, 31 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Wednesday, 13 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Wednesday, 13 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Wednesday, 13 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] event.movementX is always zero in pointerup event. (#344) (Sunday, 10 January)
• Re: [pointerevents] event.movementX is always zero in pointerup event. (#344) (Sunday, 10 January)
• [pointerevents] event.movementX is always zero in pointerup event. (#344) (Sunday, 10 January)

Liviu Tinta via GitHub

• [pointerevents] Order of pointer events across frames when using pointer capture (#355) (Wednesday, 31 March)
• Re: [pointerevents] gotpointercapture/lostpointercapture might never fire (#354) (Friday, 12 March)
• Re: [pointerevents] gotpointercapture/lostpointercapture might never fire (#354) (Wednesday, 10 March)
• [pointerevents] Pull Request: gotpointercapture/lostpointercapture might never fire (Wednesday, 10 March)

Mark Salsbery via GitHub

• Re: [pointerevents] Release Implicit Capture, Capture at Ancestor Element (#327) (Tuesday, 23 March)
• Re: [pointerevents] Release Implicit Capture, Capture at Ancestor Element (#327) (Tuesday, 23 March)

Mustaq Ahmed via GitHub

• Re: [pointerevents] Reword/expand touch-action definition (#349) (Monday, 29 March)
• Closed: [pointerevents] Some tests don't work properly with mobile-sized viewports (#139) (Tuesday, 16 February)
• Re: [pointerevents] Some tests don't work properly with mobile-sized viewports (#139) (Tuesday, 16 February)
• Re: [pointerevents] Could we ever do implicit capture for all pointer types? (#125) (Thursday, 4 February)
• Closed: [pointerevents] Reserved pointerIds for special cases (#343) (Tuesday, 12 January)
• Re: [pointerevents] Reserved pointerIds for special cases (#343) (Tuesday, 12 January)
• Re: [pointerevents] Change reserved pointerId for non-pointer events from 0 to -1 (#345) (Tuesday, 12 January)
• Re: [pointerevents] Change reserved pointerId for non-pointer events from 0 to -1 (#345) (Tuesday, 12 January)
• Re: [pointerevents] Reserved pointerIds for special cases (#343) (Tuesday, 12 January)

Navid Zolghadr via GitHub

• Re: [pointerevents] gotpointercapture/lostpointercapture might never fire (#354) (Thursday, 11 March)
• Re: [pointerevents] gotpointercapture/lostpointercapture might never fire (#354) (Wednesday, 10 March)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)

Patrick H. Lauke

• Minutes from Pointer Events WG call 17 March 2021 (Wednesday, 17 March)
• Pointer Events WG call 17 March 2021 (Tuesday, 16 March)
• Minutes from Pointer Events WG call 3 March 2021 (Wednesday, 3 March)
• Pointer Events WG call 3 March 2021 (Tuesday, 2 March)
• Re: CfC - recharter of the Pointer Events WG (ends Feb 24) (Wednesday, 24 February)
• Re: [W3C onboarding] Welcome to the Pointer Events Working Group (Saturday, 20 February)
• Minutes from Pointer Events WG call 17 February 2021 (Wednesday, 17 February)
• CfC - recharter of the Pointer Events WG (ends Feb 24) (Wednesday, 17 February)
• Re: Pointer Events WG call 17 February 2021 (Tuesday, 16 February)
• Pointer Events WG call 17 February 2021 (Tuesday, 16 February)
• PEP officially retired (Wednesday, 10 February)
• Minutes from Pointer Events WG call 3 February 2021 (Wednesday, 3 February)
• Pointer Events WG call 3 February 2021 (Wednesday, 3 February)

Patrick H. Lauke via GitHub

• Re: [pointerevents] Reword/expand touch-action definition (#349) (Wednesday, 31 March)
• Re: [pointerevents] Reword/expand touch-action definition (#349) (Wednesday, 31 March)
• Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350) (Wednesday, 31 March)
• Re: [pointerevents] Reword/expand touch-action definition (#349) (Wednesday, 31 March)
• Re: [pointerevents] The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec (#229) (Tuesday, 30 March)
• Re: [pointerevents] Specify exactly how event coalescing works (#328) (Tuesday, 30 March)
• Re: [pointerevents] Reword/expand touch-action definition (#349) (Monday, 29 March)
• Re: [pointerevents] Multi-pen support (#353) (Tuesday, 2 March)
• Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350) (Monday, 1 March)
• Re: [pointerevents] Click event while a pointer event is captured (#75) (Monday, 22 February)
• Re: [pointerevents] Click event while a pointer event is captured (#75) (Monday, 22 February)
• Closed: [pointerevents] touch-action and scrolling directional lock (#303) (Friday, 19 February)
• [pointerevents] new commits pushed by patrickhlauke (Friday, 19 February)
• [pointerevents] new commits pushed by patrickhlauke (Thursday, 18 February)
• Re: [pointerevents] Update acknowledgements, revision list, small typo, cleanup (#352) (Thursday, 18 February)
• [pointerevents] Pull Request: Update acknowledgements, revision list, small typo (Thursday, 18 February)
• Re: [pointerevents] Add a SHOULD clause about pan gestures and what happens if a gesture … (#351) (Wednesday, 17 February)
• Re: [pointerevents] Some tests don't work properly with mobile-sized viewports (#139) (Tuesday, 16 February)
• Re: [pointerevents] Add a SHOULD clause about pan gestures and what happens if a gesture … (#351) (Tuesday, 16 February)
• Re: [pointerevents] Add a SHOULD clause about pan gestures and what happens if a gesture … (#351) (Tuesday, 16 February)
• [pointerevents] Pull Request: Add a SHOULD clause about pan gestures and what happens if a gesture … (Tuesday, 16 February)
• Re: [pointerevents] Click event while a pointer event is captured (#75) (Tuesday, 16 February)
• Re: [pointerevents] Some tests don't work properly with mobile-sized viewports (#139) (Tuesday, 16 February)
• Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350) (Tuesday, 16 February)
• Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350) (Tuesday, 16 February)
• [pointerevents] Pull Request: Major refactoring: refer to "direct manipulation" rather than "touch" (Tuesday, 16 February)
• Closed: [pointerevents] Expand note about `click` / `contextmenu` (#292) (Tuesday, 16 February)
• [pointerevents] new commits pushed by patrickhlauke (Tuesday, 16 February)
• Re: [pointerevents] `touch-action: none` definition is too vague (#276) (Tuesday, 16 February)
• [pointerevents] Pull Request: Reword/expand touch-action definition (Tuesday, 16 February)
• [pointerevents] Pull Request: Add more info to note about click/contextmenu and user agent heuristics (Tuesday, 16 February)
• Closed: [pointerevents] Could we ever do implicit capture for all pointer types? (#125) (Thursday, 4 February)
• Re: [pointerevents] Could we ever do implicit capture for all pointer types? (#125) (Thursday, 4 February)
• Re: [pointerevents] Mouse back/forward buttons: page navigation or JS events? (#191) (Wednesday, 3 February)
• Closed: [pointerevents] Mouse back/forward buttons: page navigation or JS events? (#191) (Wednesday, 3 February)
• Re: [pointerevents] Could we ever do implicit capture for all pointer types? (#125) (Wednesday, 3 February)
• Re: [pointerevents] Standardize CSS pseudoclass behavior for touch (#123) (Monday, 1 February)
• Re: [pointerevents] touch-action - incorrect values in note for pull-to-refresh? (#41) (Wednesday, 20 January)
• [pointerevents] new commits pushed by patrickhlauke (Monday, 18 January)
• [pointerevents] Pull Request: Reword note about primary/non-primary pointers (Sunday, 17 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Closed: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• Re: [pointerevents] Should pointerover and pointerenter work on mobile? (#346) (Tuesday, 12 January)
• [pointerevents] new commits pushed by patrickhlauke (Tuesday, 12 January)
• Re: [pointerevents] Change reserved pointerId for non-pointer events from 0 to -1 (#345) (Tuesday, 12 January)
• [pointerevents] Pull Request: Change reserved pointerId for non-pointer events from 0 to -1 (Tuesday, 12 January)
• Re: [pointerevents] Reserved pointerIds for special cases (#343) (Tuesday, 12 January)
• Re: [pointerevents] event.movementX is always zero in pointerup event. (#344) (Sunday, 10 January)
• Closed: [pointerevents] event.movementX is always zero in pointerup event. (#344) (Sunday, 10 January)

Philippe Le Hegaret via GitHub

• Re: [pointerevents] Add a SHOULD clause about pan gestures and what happens if a gesture … (#351) (Wednesday, 17 February)

Rick Byers via GitHub

• Re: [pointerevents] Standardize CSS pseudoclass behavior for touch (#123) (Monday, 1 February)

Scott Low via GitHub

• [pointerevents] Multi-pen support (#353) (Tuesday, 2 March)

Simon Fraser via GitHub

• Re: [pointerevents] Specify exactly how event coalescing works (#328) (Wednesday, 3 February)

smaug---- via GitHub

• [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356) (Wednesday, 31 March)
• Re: [pointerevents] The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec (#229) (Wednesday, 31 March)
• Re: [pointerevents] Click event while a pointer event is captured (#75) (Monday, 22 February)
• Re: [pointerevents] Click event while a pointer event is captured (#75) (Monday, 22 February)
• Re: [pointerevents] Specify exactly how event coalescing works (#328) (Wednesday, 3 February)
• Re: [pointerevents] Click event while a pointer event is captured (#75) (Wednesday, 3 February)
• Re: [pointerevents] Specify exactly how event coalescing works (#328) (Wednesday, 3 February)
• Re: [pointerevents] Reserved pointerIds for special cases (#343) (Monday, 4 January)
• Re: [pointerevents] Reserved pointerIds for special cases (#343) (Monday, 4 January)

W3C Calendar

• Event Invitation: Pointer Events WG call (Tuesday, 30 March)
• Event Changed: Pointer Events WG call (Wednesday, 17 March)
• Event Invitation: Pointer Events WG call (Wednesday, 17 March)
• Event Confirmed: Pointer Events WG call (Tuesday, 16 March)
• Event Changed: March 17 Call (Tuesday, 16 March)
• Event Canceled: March 17 Call (Tuesday, 16 March)
• Event Changed: Monthly Call (Tuesday, 16 March)
• Event Invitation: Monthly Call (Tuesday, 16 March)

xueyuan

• Call for Participation: Pointer Events Working Group Charter Approved (Wednesday, 17 March)

Last message date: Wednesday, 31 March 2021 17:27:49 UTC