Pointer Events Working Group - Activity in 2021
No matches.
TR publications
-
6 documents published.
-
Pointer Events published 6 times as a Working Draft. History of Pointer Events
-
Past meetings
GitHub
w3c/pointerevents
-
1 issue closed.
-
Notes with normative (SHOULD/MUST) statements w3c/pointerevents#405.
-
-
2 issues received 6 new comments.
-
Standardize layerX/layerY on MouseEvent w3c/pointerevents#626 (5 comments by @chrishtr, @mfreed7, @smfr)
-
How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit w3c/pointerevents#223 (1 comment by @smaug----)
-
-
7 pull requests opened.
-
Specify event constructing steps when coalesced/predicted events are passed using the PointerEventInit w3c/pointerevents#427, by @smaug----.
-
Event constructor issue 223 w3c/pointerevents#426, by @smaug----.
-
Add labels to axes in `altitudeAngle`/`azimuthAngle` diagrams w3c/pointerevents#425, by @patrickhlauke.
-
Reword `altitudeAngle` note w3c/pointerevents#424, by @patrickhlauke.
-
Improve illustrations w3c/pointerevents#423, by @patrickhlauke.
-
Reword altitudeAngle note, expand tiltX and tiltY explanation w3c/pointerevents#422, by @patrickhlauke.
-
Update tiltX/tiltY illustrations w3c/pointerevents#421, by @patrickhlauke.
-
-
6 pull requests merged.
-
Reword `altitudeAngle` note w3c/pointerevents#424.
-
Add labels to axes in `altitudeAngle`/`azimuthAngle` diagrams w3c/pointerevents#425.
-
Reword altitudeAngle note, expand tiltX and tiltY explanation w3c/pointerevents#422.
-
Improve illustrations w3c/pointerevents#423.
-
Remove should from boundary events note and move to normative must. w3c/pointerevents#419.
-
Update tiltX/tiltY illustrations w3c/pointerevents#421.
-
-
1 pull request closed.
-
Event constructor issue 223 w3c/pointerevents#426.
-
-
3 pull requests received 5 new comments.
-
Remove should from boundary events note and move to normative must. w3c/pointerevents#419 (2 comments by @patrickhlauke)
Past meetings
-
1 meeting.
Participants
-
1 participant left.
-
Navid Zolghadr (Google LLC) left.
-
GitHub
w3c/pointerevents
-
5 issues received 6 new comments.
-
Why is 'touch-events: pan' not a value? w3c/pointerevents#420 (2 comments by @mustaqahmed, @patrickhlauke)
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers w3c/pointerevents#285 (1 comment by @patrickhlauke)
-
-
1 pull request received 4 new comments.
-
Remove should from boundary events note and move to normative must. w3c/pointerevents#419 (4 comments by @flackr, @patrickhlauke)
-
TR publications
-
2 documents published.
-
Pointer Events published twice as a Working Draft. History of Pointer Events
-
Past meetings
-
1 meeting.
GitHub
w3c/pointerevents
-
1 issue opened.
-
Why is 'touch-events: pan' not a value? w3c/pointerevents#420, by @fantasai.
-
-
1 issue reopened.
-
Introduce contextmenuclose or similar event. w3c/pointerevents#615, by @mustaqahmed.
-
-
3 issues received 12 new comments.
-
Introduce contextmenuclose or similar event. w3c/pointerevents#615 (6 comments by @flackr, @mustaqahmed)
-
`touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. w3c/pointerevents#387 (3 comments by @patrickhlauke, @trusktr)
-
-
3 pull requests opened.
-
Remove should from boundary events note and move to normative must. w3c/pointerevents#419, by @flackr.
-
Make fact that click/contextmenu are not compat mouse events normative w3c/pointerevents#418, by @patrickhlauke.
-
Remove redundant (and now wrong) note about active pointer id w3c/pointerevents#417, by @patrickhlauke.
-
-
3 pull requests merged.
-
Make fact that click/contextmenu are not compat mouse events normative w3c/pointerevents#418.
-
Remove redundant (and now wrong) note about active pointer id w3c/pointerevents#417.
-
Move elements of `pointerId` informative note to normative text w3c/pointerevents#411.
-
-
2 pull requests received 7 new comments.
-
Make fact that click/contextmenu are not compat mouse events normative w3c/pointerevents#418 (5 comments by @mustaqahmed, @patrickhlauke)
-
Remove should from boundary events note and move to normative must. w3c/pointerevents#419 (2 comments by @patrickhlauke)
-
TR publications
-
4 documents published.
-
Pointer Events published 4 times as a Working Draft. History of Pointer Events
-
Past meetings
GitHub
w3c/pointerevents
-
1 issue opened.
-
Relationship between main pointer event and coalesced events w3c/pointerevents#409, by @jakearchibald.
-
-
1 issue closed.
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100.
-
-
4 issues received 26 new comments.
-
Relationship between main pointer event and coalesced events w3c/pointerevents#409 (20 comments by @flackr, @jakearchibald, @mustaqahmed, @NavidZ, @patrickhlauke)
-
Notes with normative (SHOULD/MUST) statements w3c/pointerevents#405 (4 comments by @mustaqahmed, @patrickhlauke)
-
Should triggering the contextmenu with the mouse cause a pointercancel? w3c/pointerevents#408 (1 comment by @jakearchibald)
-
-
7 pull requests opened.
-
Reword legacy properties note to remove the "must" w3c/pointerevents#416, by @patrickhlauke.
-
Remove may/should from note about complex gestures w3c/pointerevents#415, by @patrickhlauke.
-
Make note about buttons/buttons and compat events normative w3c/pointerevents#414, by @patrickhlauke.
-
Make note about UAs not firing compat events if they support touch events normative w3c/pointerevents#413, by @patrickhlauke.
-
Move first part of the note about dispatched event order into normative text w3c/pointerevents#412, by @patrickhlauke.
-
Move elements of `pointerId` informative note to normative text w3c/pointerevents#411, by @patrickhlauke.
-
Make "Converting..." section normative w3c/pointerevents#410, by @patrickhlauke.
-
-
7 pull requests merged.
-
Make note about buttons/buttons and compat events normative w3c/pointerevents#414.
-
Make note about UAs not firing compat events if they support touch events normative w3c/pointerevents#413.
-
Move first part of the note about dispatched event order into normative text w3c/pointerevents#412.
-
Reword legacy properties note to remove the "must" w3c/pointerevents#416.
-
Remove may/should from note about complex gestures w3c/pointerevents#415.
-
Make "Converting..." section normative w3c/pointerevents#410.
-
Add note about rounding coordinates for click, auxclick, contextmenu w3c/pointerevents#404.
-
-
5 pull requests received 17 new comments.
-
Make note about UAs not firing compat events if they support touch events normative w3c/pointerevents#413 (6 comments by @mustaqahmed, @patrickhlauke)
-
Move elements of `pointerId` informative note to normative text w3c/pointerevents#411 (5 comments by @mustaqahmed, @patrickhlauke)
-
Make note about buttons/buttons and compat events normative w3c/pointerevents#414 (2 comments by @patrickhlauke)
-
Move first part of the note about dispatched event order into normative text w3c/pointerevents#412 (2 comments by @patrickhlauke)
-
Make "Converting..." section normative w3c/pointerevents#410 (2 comments by @mustaqahmed, @patrickhlauke)
-
TR publications
-
5 documents published.
-
Pointer Events published 5 times as a Working Draft. History of Pointer Events
-
Past meetings
GitHub
w3c/pointerevents
-
6 issues opened.
-
Introduce contextmenuclose or similar event. w3c/pointerevents#615, by @flackr.
-
Should triggering the contextmenu with the mouse cause a pointercancel? w3c/pointerevents#408, by @jakearchibald.
-
Lost pointer issue - spec or browser bug? w3c/pointerevents#407, by @jakearchibald.
-
Notes with normative (SHOULD/MUST) statements w3c/pointerevents#405, by @patrickhlauke.
-
Clarify which steps constitute canceling a pointer w3c/pointerevents#400, by @mustaqahmed.
-
-
3 issues closed.
-
Add note explicitly about mouse compat events, preventDefault, and passive events w3c/pointerevents#369.
-
"A user agent" vs "the user agent" w3c/pointerevents#399.
-
HTML monkeypatching: initiate the drag-and-drop operation definition w3c/pointerevents#384.
-
-
10 issues received 23 new comments.
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356 (6 comments by @jakearchibald, @smaug----)
-
Lost pointer issue - spec or browser bug? w3c/pointerevents#407 (5 comments by @jakearchibald, @nstepien, @vdwijngaert)
-
Multi-pen support and persistent pointerId w3c/pointerevents#353 (3 comments by @bmathwig, @patrickhlauke)
-
Should triggering the contextmenu with the mouse cause a pointercancel? w3c/pointerevents#408 (2 comments by @jakearchibald, @patrickhlauke)
-
Notes with normative (SHOULD/MUST) statements w3c/pointerevents#405 (2 comments by @bmathwig, @patrickhlauke)
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (1 comment by @karlcow)
-
Click event is not fired when the node is removed and then added back w3c/pointerevents#576 (1 comment by @smaug----)
-
-
5 pull requests opened.
-
Move definition point for PointerEvent w3c/pointerevents#406, by @patrickhlauke.
-
Add note about rounding coordinates for click, auxclick, contextmenu w3c/pointerevents#404, by @patrickhlauke.
-
Expand prose about preventing compatibility mouse events and make it normative w3c/pointerevents#403, by @patrickhlauke.
-
Change instances of "a user agent" to "the user agent" w3c/pointerevents#402, by @patrickhlauke.
-
Internal references cleanup, adding () to methods w3c/pointerevents#401, by @patrickhlauke.
-
-
5 pull requests merged.
-
Expand prose about preventing compatibility mouse events and make it normative w3c/pointerevents#403.
-
Move definition point for PointerEvent w3c/pointerevents#406.
-
Change instances of "a user agent" to "the user agent" w3c/pointerevents#402.
-
Internal references cleanup, adding () to methods w3c/pointerevents#401.
-
Clarify `pointercancel` firing behavior on drag. w3c/pointerevents#398.
-
-
3 pull requests received 25 new comments.
-
Add note about rounding coordinates for click, auxclick, contextmenu w3c/pointerevents#404 (20 comments by @flackr, @mustaqahmed, @patrickhlauke)
-
Expand prose about preventing compatibility mouse events and make it normative w3c/pointerevents#403 (4 comments by @patrickhlauke, @smaug----)
-
Change instances of "a user agent" to "the user agent" w3c/pointerevents#402 (1 comment by @patrickhlauke)
-
TR publications
-
3 documents published.
-
Pointer Events published 3 times as a Working Draft. History of Pointer Events
-
Past meetings
Participants
-
1 participant left.
-
Grisha Lyukshin (Microsoft Corporation) left.
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
"A user agent" vs "the user agent" w3c/pointerevents#399, by @mustaqahmed.
-
Update predicted event list definition to handle trusted vs untrusted events w3c/pointerevents#392, by @smaug----.
-
-
11 issues closed.
-
Difficulty understanding getCoalescedEvents definition w3c/pointerevents#215.
-
Unclear note about PointerEvent initialization of attributes to reflect coalesced events w3c/pointerevents#374.
-
Release Implicit Capture, Capture at Ancestor Element w3c/pointerevents#327.
-
Update predicted event list definition to handle trusted vs untrusted events w3c/pointerevents#392.
-
Do user agents only coalesce pointermove events relating to changes in position? w3c/pointerevents#375.
-
Immediately firing coalesced events for enter/leave/over/out? w3c/pointerevents#278.
-
Clarify whether touch contact must fire a `pointerrawupdate` event w3c/pointerevents#373.
-
-
10 issues received 16 new comments.
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356 (4 comments by @flackr, @mustaqahmed)
-
mousemove and preventDefault() w3c/pointerevents#638 (3 comments by @justanotheranonymoususer, @saschanaz)
-
HTML monkeypatching: initiate the drag-and-drop operation definition w3c/pointerevents#384 (2 comments by @domenic, @mustaqahmed)
-
Click event is not fired when the node is removed and then added back w3c/pointerevents#576 (1 comment by @mustaqahmed)
-
Release Implicit Capture, Capture at Ancestor Element w3c/pointerevents#327 (1 comment by @patrickhlauke)
-
`touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. w3c/pointerevents#387 (1 comment by @patrickhlauke)
-
Immediately firing coalesced events for enter/leave/over/out? w3c/pointerevents#278 (1 comment by @patrickhlauke)
-
Clarify whether touch contact must fire a `pointerrawupdate` event w3c/pointerevents#373 (1 comment by @patrickhlauke)
-
"This API always returns at least one coalesced event for pointermove events and an empty list for other types of PointerEvents." w3c/pointerevents#224 (1 comment by @smaug----)
-
The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec w3c/pointerevents#229 (1 comment by @smaug----)
-
-
8 pull requests opened.
-
Clarify `pointercancel` firing behavior on drag. w3c/pointerevents#398, by @mustaqahmed.
-
Remove note about movementX/movementY and coalesced events w3c/pointerevents#397, by @patrickhlauke.
-
Normalize title case used w3c/pointerevents#396, by @patrickhlauke.
-
Tweaks to coalesced/predicted events section w3c/pointerevents#395, by @patrickhlauke.
-
Change "event list" to "events list" w3c/pointerevents#394, by @patrickhlauke.
-
Tweak definition of predicted events to deal with untrusted events w3c/pointerevents#393, by @patrickhlauke.
-
Tweak the definition of coalesced event list to deal with untrusted e… w3c/pointerevents#391, by @smaug----.
-
Update targets of predicted and coalesced events when trusted event target changes. w3c/pointerevents#390, by @flackr.
-
-
8 pull requests merged.
-
Tweaks to coalesced/predicted events section w3c/pointerevents#395.
-
Remove note about movementX/movementY and coalesced events w3c/pointerevents#397.
-
Normalize title case used w3c/pointerevents#396.
-
Change "event list" to "events list" w3c/pointerevents#394.
-
Tweak definition of predicted events to deal with untrusted events w3c/pointerevents#393.
-
Expand explanation for non-coalesced events w3c/pointerevents#379.
-
Tweak the definition of coalesced event list to deal with untrusted e… w3c/pointerevents#391.
-
Update targets of predicted and coalesced events when trusted event target changes. w3c/pointerevents#390.
-
-
1 pull request closed.
-
Simplify/clarify coalesced and predicted events w3c/pointerevents#377.
-
-
1 pull request reopened.
-
Remove note about movementX/movementY and coalesced events w3c/pointerevents#397, by @patrickhlauke.
-
-
7 pull requests received 39 new comments.
-
Tweaks to coalesced/predicted events section w3c/pointerevents#395 (21 comments by @flackr, @mustaqahmed, @patrickhlauke)
-
Update targets of predicted and coalesced events when trusted event target changes. w3c/pointerevents#390 (7 comments by @flackr, @mustaqahmed, @patrickhlauke, @smaug----)
-
Expand explanation for non-coalesced events w3c/pointerevents#379 (6 comments by @flackr, @patrickhlauke)
-
Remove note about movementX/movementY and coalesced events w3c/pointerevents#397 (2 comments by @mustaqahmed, @patrickhlauke)
-
Tweak definition of predicted events to deal with untrusted events w3c/pointerevents#393 (1 comment by @patrickhlauke)
-
TR publications
-
5 documents published.
-
Pointer Events published 5 times as a Working Draft. History of Pointer Events
-
Past meetings
-
1 meeting.
GitHub
w3c/pointerevents
-
3 issues opened.
-
`touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. w3c/pointerevents#387, by @trusktr.
-
HTML monkeypatching: animation frame callbacks w3c/pointerevents#385, by @plehegar.
-
HTML monkeypatching: initiate the drag-and-drop operation definition w3c/pointerevents#384, by @plehegar.
-
-
3 issues closed.
-
HTML monkeypatching: animation frame callbacks w3c/pointerevents#385.
-
do `pointerrawupdate` events also get predicted events? w3c/pointerevents#380.
-
It is unclear how predicted events' timestamps should relate to actual dispatched events w3c/pointerevents#282.
-
-
6 issues received 9 new comments.
-
`touch-action: none` behavior is intuitive in Firefox, confusing in Chrome. The spec should be clearer. w3c/pointerevents#387 (3 comments by @patrickhlauke, @trusktr)
-
do `pointerrawupdate` events also get predicted events? w3c/pointerevents#380 (2 comments by @NavidZ, @patrickhlauke)
-
Specify WheelEvent.wheelDelta / wheelDeltaX / wheelDeltaY w3c/pointerevents#633 (1 comment by @foolip)
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356 (1 comment by @mustaqahmed)
-
Do user agents only coalesce pointermove events relating to changes in position? w3c/pointerevents#375 (1 comment by @patrickhlauke)
-
-
5 pull requests opened.
-
More minor tweaks w3c/pointerevents#389, by @plehegar.
-
Remove mention of animation frame callback w3c/pointerevents#388, by @patrickhlauke.
-
task queue is not reliable HTML concept. Use event loop instead w3c/pointerevents#386, by @plehegar.
-
Explicit note about pointerrawmove having an empty predicted event list w3c/pointerevents#383, by @patrickhlauke.
-
Expand the definition/explanation of predicted events timestamps w3c/pointerevents#382, by @patrickhlauke.
-
-
6 pull requests merged.
-
Remove mention of animation frame callback w3c/pointerevents#388.
-
More minor tweaks w3c/pointerevents#389.
-
task queue is not reliable HTML concept. Use event loop instead w3c/pointerevents#386.
-
Refreshing references using latest respec magic w3c/pointerevents#381.
-
Explicit note about pointerrawmove having an empty predicted event list w3c/pointerevents#383.
-
Expand the definition/explanation of predicted events timestamps w3c/pointerevents#382.
-
-
5 pull requests received 23 new comments.
-
Expand explanation for non-coalesced events w3c/pointerevents#379 (12 comments by @mustaqahmed, @patrickhlauke, @smaug----)
-
Remove mention of animation frame callback w3c/pointerevents#388 (3 comments by @patrickhlauke, @plehegar)
-
Simplify/clarify coalesced and predicted events w3c/pointerevents#377 (3 comments by @flackr, @patrickhlauke)
-
Refreshing references using latest respec magic w3c/pointerevents#381 (3 comments by @marcoscaceres, @patrickhlauke)
-
Explicit note about pointerrawmove having an empty predicted event list w3c/pointerevents#383 (2 comments by @NavidZ, @patrickhlauke)
-
TR publications
-
6 documents published.
-
Pointer Events published 6 times as a Working Draft. History of Pointer Events
-
Past meetings
Participants
-
2 participants left.
-
Dongwoo Joshua Im (Samsung Electronics Co., Ltd.) left.
-
Scott González (OpenJS Foundation) left.
-
GitHub
w3c/pointerevents
-
5 issues opened.
-
do `pointerrawupdate` events also get predicted events? w3c/pointerevents#380, by @patrickhlauke.
-
Specify WheelEvent.wheelDelta / wheelDeltaX / wheelDeltaY w3c/pointerevents#633, by @emilio.
-
Do user agents only coalesce pointermove events relating to changes in position? w3c/pointerevents#375, by @patrickhlauke.
-
Unclear note about PointerEvent initialization of attributes to reflect coalesced events w3c/pointerevents#374, by @patrickhlauke.
-
Clarify whether touch contact must fire a `pointerrawupdate` event w3c/pointerevents#373, by @yacinehmito.
-
-
4 issues closed.
-
disambiguate default *action* and default *behavior* in prose w3c/pointerevents#368.
-
Clarify/expand introduction to the touch-action section w3c/pointerevents#366.
-
Normatively make touch-action apply for direct-manipulation pen devices w3c/pointerevents#202.
-
-
15 issues received 43 new comments.
-
Clarify whether touch contact must fire a `pointerrawupdate` event w3c/pointerevents#373 (10 comments by @NavidZ, @patrickhlauke, @smaug----, @yacinehmito)
-
Do user agents only coalesce pointermove events relating to changes in position? w3c/pointerevents#375 (4 comments by @flackr, @patrickhlauke, @smaug----)
-
Unclear note about PointerEvent initialization of attributes to reflect coalesced events w3c/pointerevents#374 (4 comments by @flackr, @patrickhlauke, @smaug----)
-
It is unclear how predicted events' timestamps should relate to actual dispatched events w3c/pointerevents#282 (4 comments by @patrickhlauke, @smaug----)
-
How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit w3c/pointerevents#223 (4 comments by @annevk, @smaug----)
-
Clarify the coalesced/predicted targets dirty stuff, and clarify better how these events are generated/populated and when w3c/pointerevents#370 (4 comments by @patrickhlauke)
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers w3c/pointerevents#285 (3 comments by @garykac, @mustaqahmed, @patrickhlauke)
-
do `pointerrawupdate` events also get predicted events? w3c/pointerevents#380 (2 comments by @NavidZ, @patrickhlauke)
-
"This API always returns at least one coalesced event for pointermove events and an empty list for other types of PointerEvents." w3c/pointerevents#224 (2 comments by @patrickhlauke, @smaug----)
-
Specify WheelEvent.wheelDelta / wheelDeltaX / wheelDeltaY w3c/pointerevents#633 (1 comment by @masayuki-nakano)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (1 comment by @patrickhlauke)
-
Proposal: a way of tracking pointer position on pan/zoom touch-action w3c/pointerevents#339 (1 comment by @yacinehmito)
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356 (1 comment by @mustaqahmed)
-
-
5 pull requests opened.
-
Refreshing references using latest respec magic w3c/pointerevents#381, by @plehegar.
-
Expand explanation for non-coalesced events w3c/pointerevents#379, by @patrickhlauke.
-
Add figures for altitudeAngle and azimuthAngle w3c/pointerevents#378, by @patrickhlauke.
-
Simplify/clarify coalesced and predicted events w3c/pointerevents#377, by @patrickhlauke.
-
Clarify the rationale and purpose of touch-action w3c/pointerevents#376, by @patrickhlauke.
-
-
5 pull requests merged.
-
Clarify the rationale and purpose of touch-action w3c/pointerevents#376.
-
Add figures for altitudeAngle and azimuthAngle w3c/pointerevents#378.
-
Add new section explaining coalesced and predicted events w3c/pointerevents#364.
-
Major refactoring: refer to "direct manipulation" rather than "touch" w3c/pointerevents#350.
-
Update WCAG keyboard reference to latest spec version w3c/pointerevents#372.
-
-
1 pull request closed.
-
Move Navid Zoghadr to former editors w3c/pointerevents#371.
-
-
6 pull requests received 46 new comments.
-
Simplify/clarify coalesced and predicted events w3c/pointerevents#377 (24 comments by @flackr, @mustaqahmed, @patrickhlauke, @smaug----)
-
Add new section explaining coalesced and predicted events w3c/pointerevents#364 (7 comments by @patrickhlauke, @smaug----)
-
Move Navid Zoghadr to former editors w3c/pointerevents#371 (6 comments by @mustaqahmed, @NavidZ, @patrickhlauke)
-
Refreshing references using latest respec magic w3c/pointerevents#381 (4 comments by @marcoscaceres)
-
Add figures for altitudeAngle and azimuthAngle w3c/pointerevents#378 (3 comments by @mustaqahmed, @patrickhlauke)
-
Clarify the rationale and purpose of touch-action w3c/pointerevents#376 (2 comments by @mustaqahmed, @patrickhlauke)
-
Past meetings
Participants
-
1 participant joined.
-
Liviu Tinta (Google LLC) joined.
-
-
1 participant left.
-
Bo Cupp (Microsoft Corporation) left.
-
-
4 organizations joined.
-
Microsoft Corporation joined.
-
Google LLC joined.
-
TetraLogical Services Ltd joined.
-
Mozilla Foundation joined.
-
GitHub
w3c/pointerevents
-
8 issues opened.
-
Add note explicitly about mouse compat events, preventDefault, and passive events w3c/pointerevents#369, by @patrickhlauke.
-
disambiguate default *action* and default *behavior* in prose w3c/pointerevents#368, by @patrickhlauke.
-
Clarify/expand introduction to the touch-action section w3c/pointerevents#366, by @patrickhlauke.
-
Move glossary to the end of the spec w3c/pointerevents#362, by @patrickhlauke.
-
Add section explaining what coalesced and predicted events actually *are* in layperson's terms w3c/pointerevents#361, by @patrickhlauke.
-
Clarify that pointer event listeners are passive by default w3c/pointerevents#360, by @patrickhlauke.
-
Implement penover / pendown / penmove / penup events and similar for other new pointer types. w3c/pointerevents#359, by @flackr.
-
6 issues closed.
-
Clarify that pointer event listeners are passive by default w3c/pointerevents#360.
-
Move glossary to the end of the spec w3c/pointerevents#362.
-
Specify exactly how event coalescing works w3c/pointerevents#328.
-
Click event while a pointer event is captured w3c/pointerevents#75.
-
`touch-action: none` definition is too vague w3c/pointerevents#276.
-
-
1 issue reopened.
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100, by @mustaqahmed.
-
-
14 issues received 54 new comments.
-
Implement penover / pendown / penmove / penup events and similar for other new pointer types. w3c/pointerevents#359 (16 comments by @flackr, @msalsbery, @NavidZ, @patrickhlauke, @smaug----)
-
Clarify that pointer event listeners are passive by default w3c/pointerevents#360 (7 comments by @mustaqahmed, @NavidZ, @patrickhlauke, @smaug----)
-
Add section explaining what coalesced and predicted events actually *are* in layperson's terms w3c/pointerevents#361 (7 comments by @patrickhlauke)
-
touch-action: disable webview swipe back behavior w3c/pointerevents#358 (6 comments by @liamdebeasi, @lincolnthree, @NavidZ, @xfq)
-
Move glossary to the end of the spec w3c/pointerevents#362 (5 comments by @chaals, @patrickhlauke, @smaug----)
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356 (3 comments by @flackr, @patrickhlauke, @smaug----)
-
disambiguate default *action* and default *behavior* in prose w3c/pointerevents#368 (2 comments by @mustaqahmed, @patrickhlauke)
-
Clarify when lostpointercapture should fire w3c/pointerevents#357 (2 comments by @EdgarChen, @patrickhlauke)
-
Clarify the coalesced/predicted targets dirty stuff, and clarify better how these events are generated/populated and when w3c/pointerevents#370 (1 comment by @patrickhlauke)
-
Add note explicitly about mouse compat events, preventDefault, and passive events w3c/pointerevents#369 (1 comment by @mustaqahmed)
-
Enable direct pen and touch to have different touch-action behavior w3c/pointerevents#203 (1 comment by @flackr)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (1 comment by @mustaqahmed)
-
-
6 pull requests opened.
-
Update WCAG keyboard reference to latest spec version w3c/pointerevents#372, by @patrickhlauke.
-
Move Navid Zoghadr to former editors w3c/pointerevents#371, by @patrickhlauke.
-
Update readme w3c/pointerevents#367, by @patrickhlauke.
-
Improve legibility/style of pointerrawupdate section w3c/pointerevents#365, by @patrickhlauke.
-
Add new section explaining coalesced and predicted events w3c/pointerevents#364, by @patrickhlauke.
-
Move glossary to the end of the spec w3c/pointerevents#363, by @patrickhlauke.
-
-
4 pull requests merged.
-
Move glossary to the end of the spec w3c/pointerevents#363.
-
Update readme w3c/pointerevents#367.
-
Improve legibility/style of pointerrawupdate section w3c/pointerevents#365.
-
Reword/expand touch-action definition w3c/pointerevents#349.
-
-
6 pull requests received 70 new comments.
-
Add new section explaining coalesced and predicted events w3c/pointerevents#364 (39 comments by @flackr, @mustaqahmed, @patrickhlauke, @smaug----)
-
Major refactoring: refer to "direct manipulation" rather than "touch" w3c/pointerevents#350 (16 comments by @flackr, @mustaqahmed, @patrickhlauke, @smaug----)
-
Reword/expand touch-action definition w3c/pointerevents#349 (6 comments by @mustaqahmed, @patrickhlauke, @smaug----)
-
Move glossary to the end of the spec w3c/pointerevents#363 (5 comments by @patrickhlauke, @smaug----)
-
Improve legibility/style of pointerrawupdate section w3c/pointerevents#365 (3 comments by @patrickhlauke)
-
Lifecycle
-
1 charter started.
-
Chartered until 16 March 2023. Participants had to rejoin under this charter.
-
Past meetings
Participants
-
7 organizations left.
-
TetraLogical Services Ltd left.
-
Microsoft Corporation left.
-
Google LLC left.
-
Mozilla Foundation left.
-
OpenJS Foundation left.
-
TPGi left.
-
Samsung Electronics Co., Ltd. left.
-
GitHub
w3c/pointerevents
-
7 issues opened.
-
Clarify when lostpointercapture should fire w3c/pointerevents#357, by @smaug----.
-
Clarify what the target of the click event should be after capturing pointer events w3c/pointerevents#356, by @smaug----.
-
Order of pointer events across frames when using pointer capture w3c/pointerevents#355, by @liviutinta.
-
touch-action: disable webview swipe back behavior w3c/pointerevents#358, by @liamdebeasi.
-
Different click event order behavior between Firefox , ie , edge and Chrome/Safari w3c/pointerevents#634, by @TurnerXi.
-
Differentiate single click event and double click event w3c/pointerevents#582, by @jimmywarting.
-
Multi-pen support and persistent pointerId w3c/pointerevents#353, by @scottlow.
-
-
8 issues received 22 new comments.
-
mousemove and preventDefault() w3c/pointerevents#638 (8 comments by @annevk, @mbrodesser, @mustaqahmed, @rniwa, @saschanaz)
-
touch-action: disable webview swipe back behavior w3c/pointerevents#358 (5 comments by @fantasai, @liamdebeasi, @svgeesus)
-
The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec w3c/pointerevents#229 (2 comments by @patrickhlauke, @smaug----)
-
Different click event order behavior between Firefox , ie , edge and Chrome/Safari w3c/pointerevents#634 (2 comments by @masayuki-nakano, @mustaqahmed)
-
Release Implicit Capture, Capture at Ancestor Element w3c/pointerevents#327 (2 comments by @msalsbery)
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (1 comment by @karlcow)
-
-
1 pull request opened.
-
gotpointercapture/lostpointercapture might never fire w3c/pointerevents#354, by @liviutinta.
-
-
1 pull request closed.
-
gotpointercapture/lostpointercapture might never fire w3c/pointerevents#354.
-
-
3 pull requests received 23 new comments.
-
Reword/expand touch-action definition w3c/pointerevents#349 (16 comments by @mustaqahmed, @patrickhlauke, @smaug----)
-
gotpointercapture/lostpointercapture might never fire w3c/pointerevents#354 (4 comments by @liviutinta, @NavidZ)
-
Major refactoring: refer to "direct manipulation" rather than "touch" w3c/pointerevents#350 (3 comments by @mustaqahmed, @patrickhlauke)
-
Participants
-
1 participant joined.
-
Robert Flack (Google LLC) joined.
-
-
1 participant left.
-
Rick Byers (Google LLC) left.
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
[feature request] Standardize long press touch event w3c/pointerevents#631, by @Thaina.
-
-
4 issues closed.
-
Some tests don't work properly with mobile-sized viewports w3c/pointerevents#139.
-
Expand note about `click` / `contextmenu` w3c/pointerevents#292.
-
Could we ever do implicit capture for all pointer types? w3c/pointerevents#125.
-
Mouse back/forward buttons: page navigation or JS events? w3c/pointerevents#191.
-
-
1 issue reopened.
-
[feature request] Standardize long press touch event w3c/pointerevents#631, by @patrickhlauke.
-
-
10 issues received 23 new comments.
-
Click event while a pointer event is captured w3c/pointerevents#75 (6 comments by @patrickhlauke, @smaug----)
-
Some tests don't work properly with mobile-sized viewports w3c/pointerevents#139 (3 comments by @mustaqahmed, @patrickhlauke)
-
Could we ever do implicit capture for all pointer types? w3c/pointerevents#125 (3 comments by @mustaqahmed, @patrickhlauke)
-
[feature request] Standardize long press touch event w3c/pointerevents#631 (2 comments by @patrickhlauke, @Thaina)
-
Standardize CSS pseudoclass behavior for touch w3c/pointerevents#123 (2 comments by @patrickhlauke, @RByers)
-
Mouse back/forward buttons: page navigation or JS events? w3c/pointerevents#191 (1 comment by @patrickhlauke)
-
-
5 pull requests opened.
-
Update acknowledgements, revision list, small typo, cleanup w3c/pointerevents#352, by @patrickhlauke.
-
Add a SHOULD clause about pan gestures and what happens if a gesture … w3c/pointerevents#351, by @patrickhlauke.
-
Major refactoring: refer to "direct manipulation" rather than "touch" w3c/pointerevents#350, by @patrickhlauke.
-
Reword/expand touch-action definition w3c/pointerevents#349, by @patrickhlauke.
-
Add more info to note about click/contextmenu and user agent heuristics w3c/pointerevents#348, by @patrickhlauke.
-
-
3 pull requests merged.
-
Add a SHOULD clause about pan gestures and what happens if a gesture … w3c/pointerevents#351.
-
Update acknowledgements, revision list, small typo, cleanup w3c/pointerevents#352.
-
Add more info to note about click/contextmenu and user agent heuristics w3c/pointerevents#348.
-
-
4 pull requests received 18 new comments.
-
Add a SHOULD clause about pan gestures and what happens if a gesture … w3c/pointerevents#351 (8 comments by @mustaqahmed, @patrickhlauke, @plehegar)
-
Major refactoring: refer to "direct manipulation" rather than "touch" w3c/pointerevents#350 (5 comments by @mustaqahmed, @patrickhlauke)
-
Reword/expand touch-action definition w3c/pointerevents#349 (4 comments by @mustaqahmed, @patrickhlauke)
-
Update acknowledgements, revision list, small typo, cleanup w3c/pointerevents#352 (1 comment by @patrickhlauke)
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Should pointerover and pointerenter work on mobile? w3c/pointerevents#346, by @trusktr.
-
event.movementX is always zero in pointerup event. w3c/pointerevents#344, by @trusktr.
-
-
3 issues closed.
-
Reserved pointerIds for special cases w3c/pointerevents#343.
-
Should pointerover and pointerenter work on mobile? w3c/pointerevents#346.
-
event.movementX is always zero in pointerup event. w3c/pointerevents#344.
-
-
6 issues received 37 new comments.
-
Should pointerover and pointerenter work on mobile? w3c/pointerevents#346 (19 comments by @NavidZ, @patrickhlauke, @trusktr)
-
mousemove and preventDefault() w3c/pointerevents#638 (5 comments by @annevk, @mustaqahmed, @NavidZ, @saschanaz)
-
Reserved pointerIds for special cases w3c/pointerevents#343 (5 comments by @mustaqahmed, @patrickhlauke, @smaug----)
-
touch-action - incorrect values in note for pull-to-refresh? w3c/pointerevents#41 (3 comments by @danburzo, @patrickhlauke)
-
event.movementX is always zero in pointerup event. w3c/pointerevents#344 (3 comments by @patrickhlauke, @trusktr)
-
The order in which the `contextmenu` `auxclick` event is triggered w3c/pointerevents#614 (2 comments by @masayuki-nakano)
-
-
2 pull requests opened.
-
Reword note about primary/non-primary pointers w3c/pointerevents#347, by @patrickhlauke.
-
Change reserved pointerId for non-pointer events from 0 to -1 w3c/pointerevents#345, by @patrickhlauke.
-
-
2 pull requests merged.
-
Reword note about primary/non-primary pointers w3c/pointerevents#347.
-
Change reserved pointerId for non-pointer events from 0 to -1 w3c/pointerevents#345.
-
-
1 pull request received 3 new comments.
-
Change reserved pointerId for non-pointer events from 0 to -1 w3c/pointerevents#345 (3 comments by @mustaqahmed, @patrickhlauke)
-