Pointer Events Working Group - Activity in 2023
No matches.
GitHub
w3c/pointerevents
-
2 issues closed.
-
Implicit release of pointer capture on DOM removal doesn't match touch-events w3c/pointerevents#486.
-
-
3 issues received 5 new comments.
-
Expose 'inertial scrolling state' in wheel events w3c/pointerevents#587 (2 comments by @Azarattum, @DaveSeidman)
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (2 comments by @patrickhlauke)
-
-
1 pull request received 1 new comment.
Lifecycle
-
1 charter started.
-
Chartered until 7 November 2025.
-
TR publications
-
3 documents published.
-
Pointer Events published 3 times as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
1 issue closed.
-
What happens when the pointer capture target is removed from DOM? w3c/pointerevents#487.
-
-
4 issues received 11 new comments.
-
Clarify `mousedown` event target if the preceding `pointerdown` event listener removes the target w3c/pointerevents#492 (7 comments by @flackr, @masayuki-nakano, @mustaqahmed, @smaug----)
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (2 comments by @flackr, @mustaqahmed)
-
even with pointer capture on full width/height element in iframe, dragging stops working outside of iframe w3c/pointerevents#493 (1 comment by @mustaqahmed)
-
-
2 pull requests merged.
-
Explain how a removed DOM node should be handled for boundary events. w3c/pointerevents#491.
-
Handle pointer capture node removal asynchronously w3c/pointerevents#490.
-
-
2 pull requests received 13 new comments.
-
Explain how a removed DOM node should be handled for boundary events. w3c/pointerevents#491 (7 comments by @flackr, @mustaqahmed, @patrickhlauke, @smaug----)
-
Handle pointer capture node removal asynchronously w3c/pointerevents#490 (6 comments by @flackr, @mustaqahmed, @patrickhlauke)
-
TR publications
-
2 documents published.
-
Pointer Events published twice as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
3 issues opened.
-
What happens when the pointer capture target is removed from DOM? w3c/pointerevents#487, by @mustaqahmed.
-
Implicit release of pointer capture on DOM removal doesn't match touch-events w3c/pointerevents#486, by @flackr.
-
7 issues received 16 new comments.
-
What happens when the pointer capture target is removed from DOM? w3c/pointerevents#487 (4 comments by @flackr, @mustaqahmed)
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (3 comments by @flackr, @mustaqahmed, @smaug----)
-
Add support for laptop touchpads responding to the `touch-action` prop w3c/pointerevents#478 (3 comments by @NashJames, @patrickhlauke, @theres-waldo)
-
Implicit release of pointer capture on DOM removal doesn't match touch-events w3c/pointerevents#486 (3 comments by @flackr, @smaug----)
-
-
5 pull requests opened.
-
Explain how a removed DOM node should be handled for boundary events. w3c/pointerevents#491, by @flackr.
-
Handle pointer capture node removal asynchronously w3c/pointerevents#490, by @flackr.
-
Update reference from WCAG 2.1 to WCAG 2.2 w3c/pointerevents#489, by @patrickhlauke.
-
Add Robert Flack as co-editor w3c/pointerevents#488, by @patrickhlauke.
-
Use `float` instead of `double` for `altitudeAngle` and `azimuthAngle` w3c/pointerevents#485, by @jrandolf.
-
-
2 pull requests merged.
-
Add Robert Flack as co-editor w3c/pointerevents#488.
-
Update reference from WCAG 2.1 to WCAG 2.2 w3c/pointerevents#489.
-
-
1 pull request closed.
-
Use `float` instead of `double` for `altitudeAngle` and `azimuthAngle` w3c/pointerevents#485.
-
-
5 pull requests received 13 new comments.
-
Handle pointer capture node removal asynchronously w3c/pointerevents#490 (5 comments by @mustaqahmed, @patrickhlauke)
-
Add secure context criteria to pointerrawupdate and getCoalescedEvents w3c/pointerevents#318 (3 comments by @mustaqahmed, @smaug----)
-
Explain how a removed DOM node should be handled for boundary events. w3c/pointerevents#491 (1 comment by @flackr)
-
Use `float` instead of `double` for `altitudeAngle` and `azimuthAngle` w3c/pointerevents#485 (1 comment by @mustaqahmed)
-
Past meetings
-
1 meeting.
GitHub
w3c/pointerevents
-
1 issue opened.
-
Wide review for Pointer Events 3 w3c/pointerevents#482, by @plehegar.
-
-
2 issues closed.
-
[chore] Failed job: Couldn’t find “non secure context“ w3c/pointerevents#481.
-
Standardize layerX/layerY on MouseEvent w3c/pointerevents#626.
-
-
4 issues received 8 new comments.
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (1 comment by @patrickhlauke)
-
[chore] Failed job: Couldn’t find “non secure context“ w3c/pointerevents#481 (1 comment by @patrickhlauke)
-
2 pull requests opened.
-
Remove trailing commas w3c/pointerevents#484, by @patrickhlauke.
-
Move Navid to former editors w3c/pointerevents#483, by @patrickhlauke.
-
-
2 pull requests merged.
-
Remove trailing commas w3c/pointerevents#484.
-
Move Navid to former editors w3c/pointerevents#483.
-
Lifecycle
-
1 charter extension.
-
Charter extended until 31 October 2023.
-
TR publications
-
1 document published.
-
Pointer Events published as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
[chore] Failed job: Couldn’t find “non secure context“ w3c/pointerevents#481, by @plehegar.
-
Add support for laptop touchpads responding to the `touch-action` prop w3c/pointerevents#478, by @NashJames.
-
-
2 issues closed.
-
consider to change the behavior of getCoalescedEvents on non-SecureContext w3c/pointerevents#472.
-
Add support for laptop touchpads responding to the `touch-action` prop w3c/pointerevents#478.
-
-
3 issues received 5 new comments.
-
consider to change the behavior of getCoalescedEvents on non-SecureContext w3c/pointerevents#472 (2 comments by @mustaqahmed, @patrickhlauke)
-
Add support for laptop touchpads responding to the `touch-action` prop w3c/pointerevents#478 (2 comments by @patrickhlauke)
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (1 comment by @flackr)
-
-
2 pull requests opened.
-
Add clarification about coalesced events and secure/non secure context w3c/pointerevents#480, by @patrickhlauke.
-
Update README.md to point to latest editor's draft w3c/pointerevents#479, by @mustaqahmed.
-
-
1 pull request merged.
-
Update README.md to point to latest editor's draft w3c/pointerevents#479.
-
-
1 pull request closed.
-
Add clarification about coalesced events and secure/non secure context w3c/pointerevents#480.
-
-
4 pull requests received 4 new comments.
-
Add clarification about coalesced events and secure/non secure context w3c/pointerevents#480 (1 comment by @patrickhlauke)
-
Update README.md to point to latest editor's draft w3c/pointerevents#479 (1 comment by @patrickhlauke)
-
Add note about rounding coordinates for click, auxclick, contextmenu w3c/pointerevents#404 (1 comment by @mustaqahmed)
-
Move elements of `pointerId` informative note to normative text w3c/pointerevents#411 (1 comment by @mustaqahmed)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
3 issues closed.
-
Clarify when lostpointercapture should fire w3c/pointerevents#357.
-
Coordinates of a `pointercancel` event w3c/pointerevents#463.
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356.
-
-
5 issues received 12 new comments.
-
What should be the 'detail' property of pointer events? w3c/pointerevents#98 (7 comments by @mustaqahmed, @patrickhlauke, @stefnotch)
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (2 comments by @masayuki-nakano, @mustaqahmed)
-
consider to change the behavior of getCoalescedEvents on non-SecureContext w3c/pointerevents#472 (1 comment by @mustaqahmed)
-
-
1 pull request opened.
-
Editorial changes: move tilt calculation section, normalize header tags w3c/pointerevents#476, by @mustaqahmed.
-
-
3 pull requests merged.
-
Editorial changes: move tilt calculation section, normalize header tags w3c/pointerevents#476.
-
Clarify pointercancel coordinates w3c/pointerevents#473.
-
Define target and event-order for click, auxclick and contextmenu events w3c/pointerevents#474.
-
-
4 pull requests received 8 new comments.
-
Clarify pointercancel coordinates w3c/pointerevents#473 (4 comments by @mustaqahmed, @patrickhlauke)
-
Editorial changes: move tilt calculation section, normalize header tags w3c/pointerevents#476 (2 comments by @mustaqahmed)
-
Update targets of predicted and coalesced events when trusted event target changes. w3c/pointerevents#390 (1 comment by @smaug----)
-
Define target and event-order for click, auxclick and contextmenu events w3c/pointerevents#474 (1 comment by @mustaqahmed)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
Title hover before/after show event w3c/pointerevents#475, by @madprops.
-
-
2 issues closed.
-
Title hover before/after show event w3c/pointerevents#475.
-
touch-action and scrolling directional lock w3c/pointerevents#303.
-
-
2 issues reopened.
-
Coordinates of a `pointercancel` event w3c/pointerevents#463, by @mustaqahmed.
-
touch-action and scrolling directional lock w3c/pointerevents#303, by @mustaqahmed.
-
-
5 issues received 13 new comments.
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356 (5 comments by @flackr, @mustaqahmed, @patrickhlauke, @smaug----)
-
touch-action and scrolling directional lock w3c/pointerevents#303 (5 comments by @mustaqahmed, @smaug----)
-
-
2 pull requests opened.
-
Define target and event-order for click, auxclick and contextmenu events w3c/pointerevents#474, by @mustaqahmed.
-
Clarify pointercancel coordinates w3c/pointerevents#473, by @mustaqahmed.
-
-
4 pull requests received 23 new comments.
-
Define target and event-order for click, auxclick and contextmenu events w3c/pointerevents#474 (20 comments by @flackr, @mustaqahmed, @smaug----)
-
Add clarification about `pointercancel` coordinates/properties w3c/pointerevents#464 (1 comment by @mustaqahmed)
-
Add a SHOULD clause about pan gestures and what happens if a gesture … w3c/pointerevents#351 (1 comment by @mustaqahmed)
-
Expand the definition/explanation of predicted events timestamps w3c/pointerevents#382 (1 comment by @mustaqahmed)
-
Past meetings
GitHub
w3c/pointerevents
-
2 issues opened.
-
consider to change the behavior of getCoalescedEvents on non-SecureContext w3c/pointerevents#472, by @smaug----.
-
Making PointerEvents a living standard after v3? w3c/pointerevents#471, by @mustaqahmed.
-
-
5 issues received 9 new comments.
-
consider to change the behavior of getCoalescedEvents on non-SecureContext w3c/pointerevents#472 (2 comments by @mustaqahmed, @smaug----)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (2 comments by @mustaqahmed, @patrickhlauke)
-
Introduce contextmenuclose or similar event. w3c/pointerevents#615 (2 comments by @mfreed7, @mustaqahmed)
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356 (2 comments by @patrickhlauke)
-
-
2 pull requests received 6 new comments.
-
Add popover light dismiss integration w3c/pointerevents#460 (5 comments by @domenic, @flackr, @josepharhar, @patrickhlauke)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
Support for pens that report "hover distance" w3c/pointerevents#469, by @vinhowe.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Export pointer capture w3c/pointerevents#470, by @jakearchibald.
-
-
1 pull request merged.
-
Export pointer capture w3c/pointerevents#470.
-
-
1 pull request received 4 new comments.
TR publications
-
2 documents published.
-
Pointer Events published twice as a Working Draft. History of Pointer Events
-
Past meetings
GitHub
w3c/pointerevents
-
1 issue opened.
-
1 issue closed.
-
2 issues received 13 new comments.
-
Investigate if `tangentialPressure` is correctly implemented/working in browsers/documented appropriately in spec w3c/pointerevents#467 (12 comments by @mustaqahmed, @patrickhlauke, @smaug----)
-
-
3 pull requests opened.
-
Add note about `tangentialPressure` w3c/pointerevents#468, by @patrickhlauke.
-
Move note about pointerup pressure of 0 to pointerup event explanation w3c/pointerevents#466, by @patrickhlauke.
-
Make note about passive events normative body text w3c/pointerevents#465, by @patrickhlauke.
-
-
4 pull requests merged.
-
Add note about `tangentialPressure` w3c/pointerevents#468.
-
Move note about pointerup pressure of 0 to pointerup event explanation w3c/pointerevents#466.
-
Make note about passive events normative body text w3c/pointerevents#465.
-
Add clarification about `pointercancel` coordinates/properties w3c/pointerevents#464.
-
-
2 pull requests received 5 new comments.
-
Expand prose about preventing compatibility mouse events and make it normative w3c/pointerevents#403 (4 comments by @mustaqahmed, @patrickhlauke)
-
Add clarification about `pointercancel` coordinates/properties w3c/pointerevents#464 (1 comment by @patrickhlauke)
-
Past meetings
-
1 meeting.
GitHub
w3c/pointerevents
-
2 issues opened.
-
Define behavior for wheel event group when the scroll is handed off w3c/pointerevents#598, by @dlrobertson.
-
Define behavior for wheel event group when the initial target is mutated w3c/pointerevents#597, by @dlrobertson.
-
-
4 issues received 8 new comments.
-
Coordinates of a `pointercancel` event w3c/pointerevents#463 (5 comments by @mustaqahmed, @patrickhlauke, @smaug----)
-
Define behavior for wheel event group when the initial target is mutated w3c/pointerevents#597 (1 comment by @dlrobertson)
-
Extend pointer events to support raw trackpad data w3c/pointerevents#206 (1 comment by @patrickhlauke)
-
-
1 pull request opened.
-
Add clarification about `pointercancel` coordinates/properties w3c/pointerevents#464, by @patrickhlauke.
-
-
3 pull requests received 8 new comments.
-
Add note about rounding coordinates for click, auxclick, contextmenu w3c/pointerevents#404 (5 comments by @mustaqahmed, @smaug----)
-
Fix stale text around click, auxclick and contextmenu events w3c/pointerevents#456 (2 comments by @mustaqahmed, @smaug----)
-
Add clarification about `pointercancel` coordinates/properties w3c/pointerevents#464 (1 comment by @patrickhlauke)
-
Past meetings
-
1 meeting.
GitHub
w3c/pointerevents
-
5 issues received 8 new comments.
-
Extend pointer events to support raw trackpad data w3c/pointerevents#206 (2 comments by @govizlora, @patrickhlauke)
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (2 comments by @thasmo, @zcorpan)
-
pointerout even if the pointer doesn't move? w3c/pointerevents#457 (2 comments by @mustaqahmed, @smaug----)
-
Meta-issue: update WPT to cover Pointer Events Level 3 w3c/pointerevents#445 (1 comment by @patrickhlauke)
-
-
2 pull requests received 2 new comments.
-
Clarify `composed` attributes for `pointerenter` and `pointerleave` w3c/pointerevents#461 (1 comment by @mustaqahmed)