[pointerevents] new commits pushed by patrickhlauke
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] Pull Request: More minor tweaks
[pointerevents] Pull Request: Remove mention of animation frame callback
- Re: [pointerevents] Remove mention of animation frame callback (#388)
- Re: [pointerevents] Remove mention of animation frame callback (#388)
- Re: [pointerevents] Remove mention of animation frame callback (#388)
Minutes from Pointer Events WG call 23 June 2021
[pointerevents] new commits pushed by patrickhlauke
Event Invitation: Pointer Events WG call
[pointerevents] `touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. (#387)
- Re: [pointerevents] `touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. (#387)
- Re: [pointerevents] `touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. (#387)
- Re: [pointerevents] `touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. (#387)
Re: [pointerevents] `touch-action: none` definition is too vague (#276)
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] Pull Request: task queue is not reliable HTML concept. Use event loop instead
[pointerevents] HTML monkeypatching: animation frame callbacks (#385)
[pointerevents] HTML monkeypatching: initiate the drag-and-drop operation definition (#384)
[pointerevents] new commits pushed by plehegar
[pointerevents] new commits pushed by patrickhlauke
Closed: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282)
[pointerevents] new commits pushed by patrickhlauke
Event Cancelled: "Pointer Events WG call"
Cancelling upcoming PEWG meeting 9 June 2021
Event Invitation: Pointer Events WG call
Event Invitation: Pointer Events WG call
Event Invitation: Pointer Events WG call
Event Invitation: Pointer Events WG call
Weird events sequence/behaviour in Chrome/iOS
[pointerevents] Pull Request: Explicit note about pointerrawmove having an empty predicted event list
[pointerevents] Pull Request: Expand the definition/explanation of predicted events timestamps
[pointerevents] new commits pushed by plehegar
[pointerevents] Pull Request: Refreshing references using latest respec magic
- Re: [pointerevents] Refreshing references using latest respec magic (#381)
- Re: [pointerevents] Refreshing references using latest respec magic (#381)
- Re: [pointerevents] Refreshing references using latest respec magic (#381)
- Re: [pointerevents] Refreshing references using latest respec magic (#381)
Minutes from Pointer Events WG call 26 May 2021
[pointerevents] do `pointerrawupdate` events also get predicted events? (#380)
- Re: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380)
- Re: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380)
- Re: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380)
- Re: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380)
- Closed: [pointerevents] do `pointerrawupdate` events also get predicted events? (#380)
[pointerevents] Pull Request: Expand explanation for non-coalesced events
Event Invitation: Pointer Events WG call
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] new commits pushed by plehegar
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] Pull Request: Add figures for altitudeAngle and azimuthAngle
- Re: [pointerevents] Add figures for altitudeAngle and azimuthAngle (#378)
- Re: [pointerevents] Add figures for altitudeAngle and azimuthAngle (#378)
- Re: [pointerevents] Add figures for altitudeAngle and azimuthAngle (#378)
[pointerevents] Pull Request: Simplify/clarify coalesced and predicted events
- Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377)
- Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377)
- Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377)
- Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377)
- Re: [pointerevents] Simplify/clarify coalesced and predicted events (#377)
[pointerevents] Pull Request: Clarify the rationale and purpose of touch-action
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375)
- Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375)
- Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375)
- Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375)
- Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375)
- Re: [pointerevents] Do user agents only coalesce pointermove events relating to changes in position? (#375)
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374)
- Re: [pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374)
- Re: [pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374)
- Re: [pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374)
- Re: [pointerevents] Unclear note about PointerEvent initialization of attributes to reflect coalesced events (#374)
Minutes from Pointer Events WG call 12 May 2021
[pointerevents] new commits pushed by patrickhlauke
Closed: [pointerevents] Normatively make touch-action apply for direct-manipulation pen devices (#202)
Re: [pointerevents] "This API always returns at least one coalesced event for pointermove events and an empty list for other types of PointerEvents." (#224)
Re: [pointerevents] How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit (#223)
- Re: [pointerevents] How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit (#223)
- Re: [pointerevents] How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit (#223)
- Re: [pointerevents] How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit (#223)
[pointerevents] new commits pushed by plehegar
[pointerevents] new commits pushed by plehegar
Re: [pointerevents] Should events queue a task? (#197)
Re: [pointerevents] Proposal: a way of tracking pointer position on pan/zoom touch-action (#339)
Event Invitation: Pointer Events WG call
[pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
- Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)
[pointerevents] new commits pushed by patrickhlauke
Re: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282)
- Re: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282)
- Re: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282)
- Re: [pointerevents] It is unclear how predicted events' timestamps should relate to actual dispatched events (#282)
Re: [pointerevents] Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers (#285)
- Re: [pointerevents] Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers (#285)
- Re: [pointerevents] Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers (#285)
[pointerevents] Pull Request: Update WCAG keyboard reference to latest spec version
[pointerevents] Pull Request: Move Navid Zoghadr to former editors
- Re: [pointerevents] Move Navid Zoghadr to former editors (#371)
- Re: [pointerevents] Move Navid Zoghadr to former editors (#371)
- Re: [pointerevents] Move Navid Zoghadr to former editors (#371)
- Re: [pointerevents] Move Navid Zoghadr to former editors (#371)
- Re: [pointerevents] Move Navid Zoghadr to former editors (#371)
- Re: [pointerevents] Move Navid Zoghadr to former editors (#371)
- Re: [pointerevents] Move Navid Zoghadr to former editors (#371)
(belated) Minutes from Pointer Events WG call 14 April 2021
Minutes from Pointer Events WG call 28 April 2021
[pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370)
- Re: [pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370)
- Re: [pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370)
- Re: [pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370)
- Re: [pointerevents] Clarify what the coalesced/predicted targets dirty stuff is actually about (#370)
- Re: [pointerevents] Clarify the coalesced/predicted targets dirty stuff, and clarify better how these events are generated/populated and when (#370)
Event Invitation: Pointer Events WG call
[pointerevents] Add note explicitly about mouse compat events, preventDefault, and passive events (#369)
[pointerevents] disambiguate default *action* and default *behavior* in prose (#368)
- Re: [pointerevents] disambiguate default *action* and default *behavior* in prose (#368)
- Re: [pointerevents] disambiguate default *action* and default *behavior* in prose (#368)
- Closed: [pointerevents] disambiguate default *action* and default *behavior* in prose (#368)
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] Pull Request: Update readme
[pointerevents] new commits pushed by patrickhlauke
[pointerevents] Clarify/expand introduction to the touch-action section (#366)
[pointerevents] Pull Request: Improve legibility/style of pointerrawupdate section
- Re: [pointerevents] Improve legibility/style of pointerrawupdate section (#365)
- Re: [pointerevents] Improve legibility/style of pointerrawupdate section (#365)
- Re: [pointerevents] Improve legibility/style of pointerrawupdate section (#365)
[pointerevents] Pull Request: Add new section explaining coalesced and predicted events
- Re: [pointerevents] Add new section explaining coalesced and predicted events (#364)
- Re: [pointerevents] Add new section explaining coalesced and predicted events (#364)
- Re: [pointerevents] Add new section explaining coalesced and predicted events (#364)
- Re: [pointerevents] Add new section explaining coalesced and predicted events (#364)
- Re: [pointerevents] Add new section explaining coalesced and predicted events (#364)
- Re: [pointerevents] Add new section explaining coalesced and predicted events (#364)
- Re: [pointerevents] Add new section explaining coalesced and predicted events (#364)
- Re: [pointerevents] Add new section explaining coalesced and predicted events (#364)
[pointerevents] Pull Request: Move glossary to the end of the spec
- Re: [pointerevents] Move glossary to the end of the spec (#363)
- Re: [pointerevents] Move glossary to the end of the spec (#363)
- Re: [pointerevents] Move glossary to the end of the spec (#363)
[pointerevents] Move glossary to the end of the spec (#362)
- Re: [pointerevents] Move glossary to the end of the spec (#362)
- Re: [pointerevents] Move glossary to the end of the spec (#362)
- Re: [pointerevents] Move glossary to the end of the spec (#362)
- Re: [pointerevents] Move glossary to the end of the spec (#362)
- Re: [pointerevents] Move glossary to the end of the spec (#362)
- Closed: [pointerevents] Move glossary to the end of the spec (#362)
Closed: [pointerevents] Specify exactly how event coalescing works (#328)
Re: [pointerevents] Specify exactly how event coalescing works (#328)
[pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361)
- Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361)
- Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361)
- Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361)
- Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361)
- Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361)
- Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361)
- Re: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361)
- Closed: [pointerevents] Add section explaining what coalesced and predicted events actually *are* in layperson's terms (#361)
[pointerevents] Clarify that pointer event listeners are passive by default (#360)
- Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360)
- Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360)
- Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360)
- Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360)
- Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360)
- Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360)
- Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360)
- Closed: [pointerevents] Clarify that pointer event listeners are passive by default (#360)
- Re: [pointerevents] Clarify that pointer event listeners are passive by default (#360)
[pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Closed: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
- Re: [pointerevents] Implement penover / pendown / penmove / penup events and similar for other new pointer types. (#359)
Re: [pointerevents] Enable direct pen and touch to have different touch-action behavior (#203)
Closed: [pointerevents] Click event while a pointer event is captured (#75)
Re: [pointerevents] Click event while a pointer event is captured (#75)
Re: [pointerevents] Clarify when lostpointercapture should fire (#357)
Event Invitation: Pointer Events WG call
Re: [pointerevents] Should "click", "dblclick" and "contextmenu" events be PointerEvents? (#100)
Re: [pointerevents] touch-action: disable webview swipe back behavior (#358)
- Re: [pointerevents] touch-action: disable webview swipe back behavior (#358)
- Re: [pointerevents] touch-action: disable webview swipe back behavior (#358)
- Re: [pointerevents] touch-action: disable webview swipe back behavior (#358)
- Re: [pointerevents] touch-action: disable webview swipe back behavior (#358)
- Re: [pointerevents] touch-action: disable webview swipe back behavior (#358)
Closed: [pointerevents] `touch-action: none` definition is too vague (#276)
[pointerevents] new commits pushed by patrickhlauke
Re: [pointerevents] [css-touch-action] disable webview swipe back behavior (#358)
Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350)
- Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350)
- Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350)
- Re: [pointerevents] Major refactoring: refer to "direct manipulation" rather than "touch" (#350)
Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356)
- Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356)
- Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356)
- Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356)
- Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356)