Pointer Events Working Group - Activity in 2024
No matches.
TR publications
-
1 document published.
-
Pointer Events published as a Working Draft. History of Pointer Events
-
Past meetings
GitHub
w3c/pointerevents
-
3 issues opened.
-
Implicit pointer capture state after a failed explicit capture call at `pointerdown` w3c/pointerevents#534, by @mustaqahmed.
-
Back and Forward buttons not specified for MouseEvent.buttons w3c/pointerevents#628, by @CendioOssman.
-
Button order for MouseEvent.button vs MouseEvent.buttons very easy to miss w3c/pointerevents#622, by @CendioOssman.
-
-
2 issues closed.
-
Wide review for Pointer Events 3 w3c/pointerevents#482.
-
Limit the precision of floating point event fields w3c/pointerevents#517.
-
-
6 issues received 14 new comments.
-
Limit the precision of floating point event fields w3c/pointerevents#517 (4 comments by @jyasskin, @patrickhlauke, @smaug----)
-
Interop: major browsers fire click/auxclick events differently for chorded buttons w3c/pointerevents#530 (3 comments by @flackr, @mustaqahmed)
-
Mouse and Pointer events from a stationary mouse w3c/pointerevents#529 (3 comments by @flackr, @masayuki-nakano, @mustaqahmed)
-
Clarify the event target of `pointermove` if an event listener of the preceding `pointerrawupdate` explicitly release pointer capture w3c/pointerevents#509 (2 comments by @masayuki-nakano, @smaug----)
-
Back and Forward buttons not specified for MouseEvent.buttons w3c/pointerevents#628 (1 comment by @mustaqahmed)
-
-
3 pull requests opened.
-
Security/privacy addition for precision w3c/pointerevents#533, by @patrickhlauke.
-
Update boundary event behavior for a stationary pointing device. w3c/pointerevents#532, by @mustaqahmed.
-
-
1 pull request merged.
-
Security/privacy addition for precision w3c/pointerevents#533.
-
-
4 pull requests received 8 new comments.
-
Update boundary event behavior for a stationary pointing device. w3c/pointerevents#532 (1 comment by @smaug----)
TR publications
-
5 documents published.
-
Pointer Events published 3 times as a Working Draft. History of Pointer Events
-
Pointer Events published as a Working Draft. History of Pointer Events
-
Pointer Events published as a First Public Working Draft. History of Pointer Events
-
Past meetings
GitHub
w3c/pointerevents
-
4 issues opened.
-
Mandate a minimum dispatch frequency for continuous UI input events w3c/pointerevents#621, by @KingSupernova31.
-
Interop: major browsers fire click/auxclick events differently for chorded buttons w3c/pointerevents#530, by @mustaqahmed.
-
Mouse and Pointer events from a stationary mouse w3c/pointerevents#529, by @mustaqahmed.
-
[DOM integration] No state is reset on node removal w3c/pointerevents#526, by @domfarolino.
-
-
6 issues closed.
-
https://www.w3.org/TR/pointerevents/ redirects to old spec... w3c/pointerevents#506.
-
pointerout even if the pointer doesn't move? w3c/pointerevents#457.
-
[DOM integration] No state is reset on node removal w3c/pointerevents#526.
-
Ensure predicted events only use input from the current partition w3c/pointerevents#518.
-
-
13 issues received 33 new comments.
-
https://www.w3.org/TR/pointerevents/ redirects to old spec... w3c/pointerevents#506 (9 comments by @patrickhlauke, @plehegar)
-
Mouse and Pointer events from a stationary mouse w3c/pointerevents#529 (7 comments by @flackr, @masayuki-nakano, @mustaqahmed)
-
[DOM integration] No state is reset on node removal w3c/pointerevents#526 (3 comments by @domfarolino, @mustaqahmed, @smaug----)
-
Limit the precision of floating point event fields w3c/pointerevents#517 (2 comments by @flackr, @smaug----)
-
Clarify whether `pointermove` will be dispatched if `pointerrawupdate` listener removes the document w3c/pointerevents#510 (2 comments by @masayuki-nakano, @smaug----)
-
Clarify the event target of `pointermove` if an event listener of the preceding `pointerrawupdate` explicitly release pointer capture w3c/pointerevents#509 (2 comments by @masayuki-nakano, @smaug----)
-
Interop: major browsers fire click/auxclick events differently for chorded buttons w3c/pointerevents#530 (1 comment by @skobes-chromium)
-
Ensure predicted events only use input from the current partition w3c/pointerevents#518 (1 comment by @patrickhlauke)
-
Clarify what "suppressing a pointer event stream" really means w3c/pointerevents#504 (1 comment by @patrickhlauke)
-
-
2 pull requests opened.
-
Use level3 branch for level 3 and gh-pages branch for level 4. w3c/pointerevents#528, by @plehegar.
-
Clarify predicted events privacy implication w3c/pointerevents#527, by @patrickhlauke.
-
-
2 pull requests merged.
-
Use level3 branch for level 3 and gh-pages branch for level 4. w3c/pointerevents#528.
-
Clarify predicted events privacy implication w3c/pointerevents#527.
-
-
2 pull requests received 3 new comments.
-
Clarify predicted events privacy implication w3c/pointerevents#527 (2 comments by @jyasskin, @patrickhlauke)
-
TR publications
-
1 document published.
-
Pointer Events published as a Working Draft. History of Pointer Events
-
Past meetings
Participants
-
2 participants joined.
-
Adam Ettenberger (Microsoft Corporation) joined.
-
Olga Gerchikov (Microsoft Corporation) joined.
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
[css-env-1] Maximum safe area inset values to allow sliding bottom bar w3c/pointerevents#523, by @flackr.
-
-
2 issues closed.
-
Coalesced and predicted event attributes within an untrusted event w3c/pointerevents#514.
-
[css-env-1] Maximum safe area inset values to allow sliding bottom bar w3c/pointerevents#523.
-
-
7 issues received 21 new comments.
-
[touch actions] handwriting manipulation type to distinguish panning w3c/pointerevents#516 (12 comments by @adettenb, @flackr, @mustaqahmed, @ogerchikov, @patrickhlauke, @smaug----)
-
Ambiguity of the value of the `button` property for the `click` event w3c/pointerevents#513 (3 comments by @mustaqahmed, @smaug----)
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (2 comments by @ziadkh0)
-
[css-env-1] Maximum safe area inset values to allow sliding bottom bar w3c/pointerevents#523 (1 comment by @flackr)
-
Enable mouse click and drag to scroll and other pointer behavior customizations w3c/pointerevents#512 (1 comment by @bramus)
-
-
2 pull requests opened.
-
Add `handwriting` keyword to `touch-action` CSS property w3c/pointerevents#525, by @adettenb.
-
Clarify isTrusted bits in coalesced/predicted event lists w3c/pointerevents#524, by @mustaqahmed.
-
-
1 pull request merged.
-
Clarify isTrusted bits in coalesced/predicted event lists w3c/pointerevents#524.
-
-
2 pull requests received 3 new comments.
-
Clarify isTrusted bits in coalesced/predicted event lists w3c/pointerevents#524 (2 comments by @mustaqahmed)
-
GitHub
w3c/pointerevents
-
9 issues opened.
-
[event-algo] Remove "6.10. send click event" w3c/pointerevents#584, by @smaug----.
-
[PointerEvent algorithms] Dispatch of click, auxclick and contextmenu events w3c/pointerevents#522, by @mustaqahmed.
-
[PointerEvent algorithms] MouseEvents are created from PointerEvents w3c/pointerevents#521, by @mustaqahmed.
-
[PointerEvent algorithms] Remove 1:1 correspondence between Mouse and Pointer boundary events w3c/pointerevents#520, by @mustaqahmed.
-
[PointerEvent algorithms] Order of boundary events w3c/pointerevents#519, by @mustaqahmed.
-
[MouseEvent algorithms] Boundary event dispatch needs to be tied to native down and up events w3c/pointerevents#620, by @mustaqahmed.
-
Ensure predicted events only use input from the current partition w3c/pointerevents#518, by @jyasskin.
-
Limit the precision of floating point event fields w3c/pointerevents#517, by @jyasskin.
-
[touch actions] handwriting manipulation type to distinguish panning w3c/pointerevents#516, by @adettenb.
-
-
1 issue reopened.
-
pointerout even if the pointer doesn't move? w3c/pointerevents#457, by @mustaqahmed.
-
-
10 issues received 26 new comments.
-
Coalesced and predicted event attributes within an untrusted event w3c/pointerevents#514 (9 comments by @flackr, @mustaqahmed, @smaug----)
-
pointerout even if the pointer doesn't move? w3c/pointerevents#457 (5 comments by @masayuki-nakano, @mustaqahmed, @smaug----)
-
Ensure predicted events only use input from the current partition w3c/pointerevents#518 (3 comments by @jyasskin, @mustaqahmed, @patrickhlauke)
-
[touch actions] handwriting manipulation type to distinguish panning w3c/pointerevents#516 (2 comments by @adettenb, @flackr)
-
Limit the precision of floating point event fields w3c/pointerevents#517 (2 comments by @jyasskin, @mustaqahmed)
-
[PointerEvent algorithms] MouseEvents are created from PointerEvents w3c/pointerevents#521 (1 comment by @mustaqahmed)
-
[PointerEvent algorithms] Remove 1:1 correspondence between Mouse and Pointer boundary events w3c/pointerevents#520 (1 comment by @mustaqahmed)
-
[PointerEvent algorithms] Order of boundary events w3c/pointerevents#519 (1 comment by @mustaqahmed)
-
[MouseEvent algorithms] Boundary event dispatch needs to be tied to native down and up events w3c/pointerevents#620 (1 comment by @mustaqahmed)
-
Clarify whether `pointermove` will be dispatched if `pointerrawupdate` listener removes the document w3c/pointerevents#510 (1 comment by @smaug----)
-
TR publications
-
1 document published.
-
Pointer Events published as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
6 issues opened.
-
Coalesced and predicted event attributes within an untrusted event w3c/pointerevents#514, by @mustaqahmed.
-
Ambiguity of the value of the `button` property for the `click` event w3c/pointerevents#513, by @rr-codes.
-
Enable mouse click and drag to scroll and other pointer behavior customizations w3c/pointerevents#512, by @flackr.
-
-
2 issues closed.
-
Multi-pen support and persistent pointerId w3c/pointerevents#353.
-
7 issues received 15 new comments.
-
Clarify what event is `userEvent` to consider `click`/`auxclick` event target after `touchend` (or `pointerup`) w3c/pointerevents#508 (9 comments by @flackr, @masayuki-nakano, @mustaqahmed)
-
Coalesced and predicted event attributes within an untrusted event w3c/pointerevents#514 (1 comment by @mustaqahmed)
-
‘Logical’ values for the ‘touch-action’ property w3c/pointerevents#505 (1 comment by @patrickhlauke)
-
Mouse back/forward buttons: page navigation or JS events? w3c/pointerevents#632 (1 comment by @wayfarer3130)
-
-
1 pull request merged.
-
Add persistentDeviceId to PointerEvent w3c/pointerevents#495.
-
-
1 pull request received 1 new comment.
GitHub
w3c/pointerevents
-
6 issues received 13 new comments.
-
Clarify what event is `userEvent` to consider `click`/`auxclick` event target after `touchend` (or `pointerup`) w3c/pointerevents#508 (3 comments by @mustaqahmed, @smaug----)
-
Mouse coordinates represented in CSS pixels do not account for retina displays with window.devicePixelRatio > 1 w3c/pointerevents#602 (3 comments by @mustaqahmed, @RByers)
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (3 comments by @karlcow, @ziadkh0)
-
Wheel event: determine difference between trackpad and mouse events w3c/pointerevents#596 (1 comment by @marksteward)
-
https://www.w3.org/TR/pointerevents/ redirects to old spec... w3c/pointerevents#506 (1 comment by @smaug----)
-
-
2 pull requests received 5 new comments.
-
Add persistentDeviceId to PointerEvent w3c/pointerevents#495 (4 comments by @patrickhlauke, @sahirv, @smaug----)
-
GitHub
w3c/pointerevents
-
4 issues opened.
-
Clarify (or override) `dblclick` event target w3c/pointerevents#507, by @masayuki-nakano.
-
https://www.w3.org/TR/pointerevents/ redirects to old spec... w3c/pointerevents#506, by @marcoscaceres.
-
‘Logical’ values for the ‘touch-action’ property w3c/pointerevents#505, by @aphillips.
-
4 issues received 20 new comments.
-
Clarify what event is `userEvent` to consider `click`/`auxclick` event target after `touchend` (or `pointerup`) w3c/pointerevents#508 (15 comments by @flackr, @masayuki-nakano)
-
https://www.w3.org/TR/pointerevents/ redirects to old spec... w3c/pointerevents#506 (3 comments by @marcoscaceres, @patrickhlauke)
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers w3c/pointerevents#285 (1 comment by @garykac)
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (1 comment by @mustaqahmed)
-
-
1 pull request received 2 new comments.
GitHub
w3c/pointerevents
-
2 issues opened.
-
Clarify what "suppressing a pointer event stream" really means w3c/pointerevents#504, by @mustaqahmed.
-
Event sequence when long tapping an image w3c/pointerevents#503, by @lpd-au.
-
-
1 issue closed.
-
mousemove and preventDefault() w3c/pointerevents#638.
-
-
6 issues received 8 new comments.
-
pointerout even if the pointer doesn't move? w3c/pointerevents#457 (2 comments by @egirard, @mustaqahmed)
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (1 comment by @masayuki-nakano)
-
Mouse coordinates represented in CSS pixels do not account for retina displays with window.devicePixelRatio > 1 w3c/pointerevents#602 (1 comment by @RByers)
-
-
5 pull requests received 36 new comments.
-
Add persistentDeviceId to PointerEvent w3c/pointerevents#495 (32 comments by @annevk, @flackr, @ogerchikov, @sahirv, @smaug----)
-
Update targets of predicted and coalesced events when trusted event target changes. w3c/pointerevents#390 (1 comment by @smaug----)
-
Rewrite the dispatch algorithm for click-like events w3c/pointerevents#494 (1 comment by @mustaqahmed)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
Inconsistency on cancelability of dbclick w3c/pointerevents#629, by @dontcallmedom.
-
-
3 issues received 5 new comments.
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (3 comments by @masayuki-nakano, @smaug----)
-
What should be the 'detail' property of pointer events? w3c/pointerevents#98 (1 comment by @enexusde)
-
-
1 pull request received 18 new comments.
-
Add persistentDeviceId to PointerEvent w3c/pointerevents#495 (18 comments by @flackr, @mustaqahmed, @sahirv, @smaug----)
-
TR publications
-
4 documents published.
-
Pointer Events published 4 times as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
3 issues opened.
-
Selection creation sometimes causes a `pointerleave` in Safari w3c/pointerevents#501, by @pygy.
-
Status out of date in the README w3c/pointerevents#500, by @pygy.
-
improve drop down menu handling w3c/pointerevents#499, by @tienmai56.
-
-
3 issues closed.
-
Selection creation sometimes causes a `pointerleave` in Safari w3c/pointerevents#501.
-
improve drop down menu handling w3c/pointerevents#499.
-
Status out of date in the README w3c/pointerevents#500.
-
-
7 issues received 25 new comments.
-
Wide review for Pointer Events 3 w3c/pointerevents#482 (8 comments by @aphillips, @patrickhlauke, @plehegar)
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers w3c/pointerevents#285 (7 comments by @flackr, @mustaqahmed, @pygy)
-
Selection creation sometimes causes a `pointerleave` in Safari w3c/pointerevents#501 (3 comments by @aprotyas, @mustaqahmed, @pygy)
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (2 comments by @trusktr, @ziadkh0)
-
-
1 pull request opened.
-
Clarify boundary event dispatch paragraphs in 4.1.3 w3c/pointerevents#502, by @mustaqahmed.
-
-
1 pull request merged.
-
Clarify boundary event dispatch paragraphs in 4.1.3 w3c/pointerevents#502.
-
-
2 pull requests received 27 new comments.
-
Add persistentDeviceId to PointerEvent w3c/pointerevents#495 (24 comments by @flackr, @ogerchikov, @sahirv, @smaug----)
-
Clarify boundary event dispatch paragraphs in 4.1.3 w3c/pointerevents#502 (3 comments by @flackr, @mustaqahmed)
-
TR publications
-
1 document published.
-
Pointer Events published as a Working Draft. History of Pointer Events
-
Participants
-
1 participant joined.
-
TIEN MAI (Microsoft Corporation) joined.
-
GitHub
w3c/pointerevents
-
1 issue closed.
-
Update https://github.com/web-platform-tests/wpt/blob/master/pointerevents/META.yml w3c/pointerevents#498.
-
-
6 issues received 15 new comments.
-
Update https://github.com/web-platform-tests/wpt/blob/master/pointerevents/META.yml w3c/pointerevents#498 (4 comments by @patrickhlauke, @smaug----)
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356 (2 comments by @mustaqahmed)
-
Clarify `pointerleave` and `pointerout` events when first pointer move after removing an element under the pointer w3c/pointerevents#477 (1 comment by @mustaqahmed)
-
touch-action: disable webview swipe back behavior w3c/pointerevents#358 (1 comment by @lincolnthree)
-
3 pull requests received 3 new comments.
-
Define target and event-order for click, auxclick and contextmenu events w3c/pointerevents#474 (1 comment by @mustaqahmed)
-
Move elements of `pointerId` informative note to normative text w3c/pointerevents#411 (1 comment by @mustaqahmed)
-
TR publications
-
2 documents published.
-
Pointer Events published twice as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Update https://github.com/web-platform-tests/wpt/blob/master/pointerevents/META.yml w3c/pointerevents#498, by @smaug----.
-
Make `pointerenter` definition similar to `pointerover` w.r.t. `pointerdown` from a touch pointer w3c/pointerevents#497, by @mustaqahmed.
-
-
2 issues closed.
-
4 issues received 7 new comments.
-
Make `pointerenter` definition similar to `pointerover` w.r.t. `pointerdown` from a touch pointer w3c/pointerevents#497 (2 comments by @mustaqahmed, @smaug----)
-
Add logical dimension values for touch-action property, since logical is/has shipped w3c/pointerevents#272 (1 comment by @patrickhlauke)
-
-
3 pull requests opened.
-
Add logical/abstract values for `touch-action` w3c/pointerevents#496, by @patrickhlauke.
-
Add persistentDeviceId to PointerEvent w3c/pointerevents#495, by @sahirv.
-
Rewrite the dispatch algorithm for click-like events w3c/pointerevents#494, by @mustaqahmed.
-
-
1 pull request merged.
-
Rewrite the dispatch algorithm for click-like events w3c/pointerevents#494.
-
-
2 pull requests received 34 new comments.
-
Rewrite the dispatch algorithm for click-like events w3c/pointerevents#494 (29 comments by @flackr, @mustaqahmed, @patrickhlauke, @smaug----)
-
Add persistentDeviceId to PointerEvent w3c/pointerevents#495 (5 comments by @flackr, @ogerchikov, @patrickhlauke, @sahirv)
-