Pointer Events Working Group - Activity in 2020
No matches.
Lifecycle
-
1 charter extension.
-
Charter extended until 31 March 2021.
-
GitHub
w3c/pointerevents
-
3 issues opened.
-
Reserved pointerIds for special cases w3c/pointerevents#343, by @mustaqahmed.
-
The order in which the `contextmenu` `auxclick` event is triggered w3c/pointerevents#614, by @mantou132.
-
-
1 issue closed.
-
5 issues received 17 new comments.
-
Reserved pointerIds for special cases w3c/pointerevents#343 (10 comments by @liviutinta, @mustaqahmed, @patrickhlauke, @smaug----)
-
Release Implicit Capture, Capture at Ancestor Element w3c/pointerevents#327 (3 comments by @joyzhong, @msalsbery, @patrickhlauke)
-
touch-action doesn't allow for press-hold-drag UX w3c/pointerevents#178 (2 comments by @NavidZ, @patrickhlauke)
-
The order in which the `contextmenu` `auxclick` event is triggered w3c/pointerevents#614 (1 comment by @saschanaz)
-
-
1 pull request opened.
-
Typo w3c/pointerevents#341, by @patrickhlauke.
-
-
2 pull requests merged.
-
Typo w3c/pointerevents#341.
-
Change the type of click, auxclick, and contextmenu to PointerEvent w3c/pointerevents#317.
-
-
1 pull request received 9 new comments.
-
Change the type of click, auxclick, and contextmenu to PointerEvent w3c/pointerevents#317 (9 comments by @mustaqahmed, @NavidZ, @patrickhlauke, @smaug----)
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Proposal: a way of tracking pointer position on pan/zoom touch-action w3c/pointerevents#339, by @samuelmtimbo.
-
mousemove and preventDefault() w3c/pointerevents#638, by @annevk.
-
-
3 issues closed.
-
Should getCoalescedEvents() return always the same objects or new instances with same data? w3c/pointerevents#227.
-
Standardize CSS pseudoclass behavior for touch w3c/pointerevents#123.
-
Set touch-action to allow web pages opt out Android back gesture w3c/pointerevents#295.
-
-
9 issues received 15 new comments.
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers w3c/pointerevents#285 (5 comments by @NavidZ, @patrickhlauke, @samuelmtimbo, @smaug----)
-
Expose 'inertial scrolling state' in wheel events w3c/pointerevents#587 (2 comments by @aeharding, @lorenbrichter)
-
touch-action and scrolling directional lock w3c/pointerevents#303 (2 comments by @lincolnthree, @patrickhlauke)
-
touch-action doesn't allow for press-hold-drag UX w3c/pointerevents#178 (1 comment by @patrickhlauke)
-
Release Implicit Capture, Capture at Ancestor Element w3c/pointerevents#327 (1 comment by @msalsbery)
-
Set touch-action to allow web pages opt out Android back gesture w3c/pointerevents#295 (1 comment by @patrickhlauke)
-
Some tests don't work properly with mobile-sized viewports w3c/pointerevents#139 (1 comment by @patrickhlauke)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (1 comment by @garykac)
-
-
1 pull request opened.
-
Typos w3c/pointerevents#340, by @patrickhlauke.
-
-
1 pull request merged.
-
Typos w3c/pointerevents#340.
-
-
2 pull requests received 7 new comments.
-
Change the type of click, auxclick, and contextmenu to PointerEvent w3c/pointerevents#317 (5 comments by @mustaqahmed, @patrickhlauke)
-
TR publications
-
1 document published.
-
Pointer Events published as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
How pointer capture should behave on draggable element? w3c/pointerevents#338, by @EdgarChen.
-
-
2 issues closed.
-
How pointer capture should behave on draggable element? w3c/pointerevents#338.
-
Please don't <dfn> Element w3c/pointerevents#333.
-
-
4 issues received 7 new comments.
-
How pointer capture should behave on draggable element? w3c/pointerevents#338 (3 comments by @NavidZ, @patrickhlauke)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (1 comment by @liviutinta)
-
-
2 pull requests opened.
-
Re-enable automatic publishing w3c/pointerevents#337, by @plehegar.
-
Editorial: remove bad dfn overrides w3c/pointerevents#336, by @marcoscaceres.
-
-
2 pull requests merged.
-
Re-enable automatic publishing w3c/pointerevents#337.
-
Editorial: remove bad dfn overrides w3c/pointerevents#336.
-
-
2 pull requests received 6 new comments.
-
Change the type of click, auxclick, and contextmenu to PointerEvent w3c/pointerevents#317 (4 comments by @liviutinta, @NavidZ, @smaug----)
-
TR publications
-
1 document published.
-
Pointer Events published as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Please don't <dfn> Element w3c/pointerevents#333, by @annevk.
-
Mouse back/forward buttons: page navigation or JS events? w3c/pointerevents#632, by @smaug----.
-
-
2 issues closed.
-
The behavior of `touch-action: none` on <iframe> is unclear w3c/pointerevents#325.
-
setPointerCapture should be disabled in sandboxed iframes by default w3c/pointerevents#16.
-
-
7 issues received 17 new comments.
-
The behavior of `touch-action: none` on <iframe> is unclear w3c/pointerevents#325 (6 comments by @mustaqahmed, @patrickhlauke, @smaug----, @staktrace)
-
Stylus eraser: should it be a new pointerType instead of a button state? w3c/pointerevents#134 (2 comments by @patrickhlauke, @smaug----)
-
setPointerCapture should be disabled in sandboxed iframes by default w3c/pointerevents#16 (1 comment by @patrickhlauke)
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers w3c/pointerevents#285 (1 comment by @smaug----)
-
Mouse back/forward buttons: page navigation or JS events? w3c/pointerevents#191 (1 comment by @patrickhlauke)
-
-
5 pull requests opened.
-
Simplified config for group w3c/pointerevents#335, by @plehegar.
-
Add note about touch-action and iframe/embedded browsing contexts w3c/pointerevents#334, by @patrickhlauke.
-
Fixed MDN config, per https://github.com/w3c/respec/wiki/mdn w3c/pointerevents#332, by @plehegar.
-
Config for ECHIDNA and travis w3c/pointerevents#331, by @plehegar.
-
Use defer and make sure to point to patent policy 2020 w3c/pointerevents#330, by @plehegar.
-
-
5 pull requests merged.
-
Simplified config for group w3c/pointerevents#335.
-
Add note about touch-action and iframe/embedded browsing contexts w3c/pointerevents#334.
-
Config for ECHIDNA and travis w3c/pointerevents#331.
-
Fixed MDN config, per https://github.com/w3c/respec/wiki/mdn w3c/pointerevents#332.
-
Use defer and make sure to point to patent policy 2020 w3c/pointerevents#330.
-
-
2 pull requests received 2 new comments.
-
Use defer and make sure to point to patent policy 2020 w3c/pointerevents#330 (1 comment by @patrickhlauke)
Participants
-
1 chair appointed.
-
Patrick Lauke became a chair.
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Specify exactly how event coalescing works w3c/pointerevents#328, by @smfr.
-
Release Implicit Capture, Capture at Ancestor Element w3c/pointerevents#327, by @msalsbery.
-
-
4 issues closed.
-
How best to inflate hit targets for touch? w3c/pointerevents#126.
-
Should DragEvent be upgraded to a PointerEvent? w3c/pointerevents#106.
-
Explore unifying web-platform-test automation logic w3c/pointerevents#120.
-
Define event order relative to RAF? w3c/pointerevents#9.
-
-
12 issues received 20 new comments.
-
Release Implicit Capture, Capture at Ancestor Element w3c/pointerevents#327 (6 comments by @liviutinta, @msalsbery, @NavidZ)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (2 comments by @mustaqahmed, @NavidZ)
-
touch-action and scrolling directional lock w3c/pointerevents#303 (2 comments by @lincolnthree, @NavidZ)
-
Need clarification how mouseenter/leave should behave while modifying DOM tree during event dispatch w3c/pointerevents#613 (2 comments by @garykac, @smaug----)
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers w3c/pointerevents#285 (1 comment by @garykac)
-
Explore unifying web-platform-test automation logic w3c/pointerevents#120 (1 comment by @patrickhlauke)
-
The behavior of `touch-action: none` on <iframe> is unclear w3c/pointerevents#325 (1 comment by @mustaqahmed)
-
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/pointerevents#329, by @autokagami.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/pointerevents#329.
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
The behavior of `touch-action: none` on <iframe> is unclear w3c/pointerevents#325, by @graouts.
-
-
3 issues closed.
-
Update spec to new IDL syntax for optional dictionaries w3c/pointerevents#296.
-
It is not possible to generate one set of angle values from other set w3c/pointerevents#321.
-
should altitudeAngle default to 0 or pi/2 when not supported? w3c/pointerevents#320.
-
-
12 issues received 24 new comments.
-
Need clarification how mouseenter/leave should behave while modifying DOM tree during event dispatch w3c/pointerevents#613 (4 comments by @garykac, @smaug----)
-
Add WheelEvent#wheelDelta/wheelDeltaX/wheelDeltaY w3c/pointerevents#590 (4 comments by @foolip, @mustaqahmed)
-
Update spec to new IDL syntax for optional dictionaries w3c/pointerevents#296 (3 comments by @Ms2ger, @patrickhlauke)
-
tiltX and tiltY aren't as helpful as just having altitude angle w3c/pointerevents#274 (2 comments by @grorg, @patrickhlauke)
-
The behavior of `touch-action: none` on <iframe> is unclear w3c/pointerevents#325 (2 comments by @mustaqahmed, @patrickhlauke)
-
It is not possible to generate one set of angle values from other set w3c/pointerevents#321 (2 comments by @NavidZ, @patrickhlauke)
-
Clarify whether a click event should be dispatched for `control` + click in Mac OS w3c/pointerevents#581 (2 comments by @EdgarChen, @garykac)
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers w3c/pointerevents#285 (1 comment by @patrickhlauke)
-
should altitudeAngle default to 0 or pi/2 when not supported? w3c/pointerevents#320 (1 comment by @patrickhlauke)
-
-
1 pull request opened.
-
Change PHL company affiliation w3c/pointerevents#326, by @patrickhlauke.
-
-
3 pull requests merged.
-
Change PHL company affiliation w3c/pointerevents#326.
-
Update azimuth/altitude/tiltX/tiltY to not require default values in pointer events web idl w3c/pointerevents#323.
-
Fix tilt to sperical calculation. w3c/pointerevents#324.
-
-
2 pull requests received 4 new comments.
-
Change the type of click, auxclick, and contextmenu to PointerEvent w3c/pointerevents#317 (3 comments by @patrickhlauke)
-
Update azimuth/altitude/tiltX/tiltY to not require default values in pointer events web idl w3c/pointerevents#323 (1 comment by @NavidZ)
-
Participants
-
1 chair stepped down.
-
Patrick Lauke stepped down as a chair.
-
-
1 participant joined.
-
Patrick Lauke (TetraLogical Services Ltd) joined.
-
-
1 participant left.
-
Patrick Lauke (TetraLogical Services Ltd) left.
-
-
1 organization joined.
-
TetraLogical Services Ltd joined.
-
GitHub
w3c/pointerevents
-
1 pull request opened.
-
Fix tilt to sperical calculation. w3c/pointerevents#324, by @mustaqahmed.
-
-
2 pull requests received 16 new comments.
-
Update azimuth/altitude/tiltX/tiltY to not require default values in pointer events web idl w3c/pointerevents#323 (15 comments by @liviutinta, @mustaqahmed, @NavidZ)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
Clarify whether a click event should be dispatched for `control` + click in Mac OS w3c/pointerevents#581, by @EdgarChen.
-
-
2 issues received 19 new comments.
-
It is not possible to generate one set of angle values from other set w3c/pointerevents#321 (18 comments by @domenic, @NavidZ, @patrickhlauke)
-
should altitudeAngle default to 0 or pi/2 when not supported? w3c/pointerevents#320 (1 comment by @patrickhlauke)
-
-
2 pull requests opened.
-
Update azimuth/altitude/tiltX/tiltY to not require default values in pointer events web idl w3c/pointerevents#323, by @liviutinta.
-
Translate between tiltX/tiltY and azimuth/altitude. Fixes #321 w3c/pointerevents#322, by @liviutinta.
-
-
1 pull request closed.
-
Translate between tiltX/tiltY and azimuth/altitude. Fixes #321 w3c/pointerevents#322.
-
-
1 pull request received 11 new comments.
-
Translate between tiltX/tiltY and azimuth/altitude. Fixes #321 w3c/pointerevents#322 (11 comments by @domenic, @liviutinta, @NavidZ, @patrickhlauke, @plehegar)
-
GitHub
w3c/pointerevents
-
3 issues opened.
-
It is not possible to generate one set of angle values from other set w3c/pointerevents#321, by @NavidZ.
-
should altitudeAngle default to 0 or pi/2 when not supported? w3c/pointerevents#320, by @patrickhlauke.
-
touch-action:none and overflow:auto w3c/pointerevents#319, by @liviutinta.
-
-
2 issues closed.
-
tiltX and tiltY aren't as helpful as just having altitude angle w3c/pointerevents#274.
-
Limit pointerrawupdate and getCoalescedEvents API to secure origins w3c/pointerevents#277.
-
-
2 issues received 9 new comments.
-
touch-action:none and overflow:auto w3c/pointerevents#319 (7 comments by @bokand, @liviutinta, @NavidZ, @theres-waldo)
-
should altitudeAngle default to 0 or pi/2 when not supported? w3c/pointerevents#320 (2 comments by @NavidZ, @patrickhlauke)
-
-
2 pull requests merged.
-
add altitudeAngle/azimuthAngle w3c/pointerevents#316.
-
Add secure context criteria to pointerrawupdate and getCoalescedEvents w3c/pointerevents#318.
-
-
2 pull requests received 26 new comments.
-
add altitudeAngle/azimuthAngle w3c/pointerevents#316 (24 comments by @liviutinta, @NavidZ, @patrickhlauke)
-
Change the type of click, auxclick, and contextmenu to PointerEvent w3c/pointerevents#317 (2 comments by @NavidZ, @patrickhlauke)
-
GitHub
w3c/pointerevents
-
2 pull requests opened.
-
Add secure context criteria to pointerrawupdate and getCoalescedEvents w3c/pointerevents#318, by @NavidZ.
-
Change the type of click, auxclick, and contextmenu to PointerEvent w3c/pointerevents#317, by @NavidZ.
-
-
2 pull requests received 17 new comments.
-
add altitudeAngle/azimuthAngle w3c/pointerevents#316 (13 comments by @liviutinta, @NavidZ, @patrickhlauke)
-
Add secure context criteria to pointerrawupdate and getCoalescedEvents w3c/pointerevents#318 (4 comments by @domenic, @NavidZ)
-
GitHub
w3c/pointerevents
-
1 issue closed.
-
Consider a simple API for low-latency pointer trails w3c/pointerevents#204.
-
-
7 issues received 9 new comments.
-
Consider a simple API for low-latency pointer trails w3c/pointerevents#204 (3 comments by @dlibby-, @patrickhlauke, @smaug----)
-
How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit w3c/pointerevents#223 (1 comment by @smaug----)
-
Should getCoalescedEvents() return always the same objects or new instances with same data? w3c/pointerevents#227 (1 comment by @smaug----)
-
Limit pointerrawupdate and getCoalescedEvents API to secure origins w3c/pointerevents#277 (1 comment by @smaug----)
-
tiltX and tiltY aren't as helpful as just having altitude angle w3c/pointerevents#274 (1 comment by @patrickhlauke)
-
-
2 pull requests opened.
-
add altitudeAngle/azimuthAngle w3c/pointerevents#316, by @patrickhlauke.
-
Various README updates w3c/pointerevents#315, by @plehegar.
-
-
1 pull request merged.
-
Various README updates w3c/pointerevents#315.
-
-
1 pull request received 1 new comment.
GitHub
w3c/pointerevents
-
1 issue opened.
-
`wheel` event listeners cannot prevent default scroll only along specific direction w3c/pointerevents#594, by @masayuki-nakano.
-