Pointer Events Working Group - Activity in 2018
No matches.
Lifecycle
-
1 charter started.
-
Chartered until 31 December 2020.
-
TR publications
-
1 document published.
-
Pointer Events published as a Candidate Recommendation Snapshot. History of Pointer Events
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Add logical dimension values for touch-action property, since logical is/has shipped w3c/pointerevents#272, by @jonjohnjohnson.
-
ReSpec complains about normative references in informative sections w3c/pointerevents#271, by @patrickhlauke.
-
-
2 issues closed.
-
ReSpec complains about normative references in informative sections w3c/pointerevents#271.
-
Pointer Capture section marked as non-normative w3c/pointerevents#269.
-
-
3 issues received 8 new comments.
-
Add logical dimension values for touch-action property, since logical is/has shipped w3c/pointerevents#272 (5 comments by @jonjohnjohnson, @NavidZ, @patrickhlauke)
-
ReSpec complains about normative references in informative sections w3c/pointerevents#271 (2 comments by @andreastt, @patrickhlauke)
-
Define a low latency event that isn't occur in the document lifecycle w3c/pointerevents#214 (1 comment by @smaug----)
-
-
1 pull request opened.
-
Pointer Capture is normative. Fix #269 w3c/pointerevents#270, by @plehegar.
-
-
1 pull request merged.
-
Pointer Capture is normative. Fix #269 w3c/pointerevents#270.
-
-
2 pull requests received 7 new comments.
-
Pointer Capture is normative. Fix #269 w3c/pointerevents#270 (4 comments by @NavidZ, @patrickhlauke, @plehegar)
-
Introduce pointerrawupdate to address the high frequency usecases w3c/pointerevents#260 (3 comments by @NavidZ)
-
TR publications
-
1 document published.
-
Pointer Events published as a Proposed Recommendation. History of Pointer Events
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
Pointer Capture section marked as non-normative w3c/pointerevents#269, by @patrickhlauke.
-
-
1 issue closed.
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Initial draft charter for PE3 w3c/pointerevents#268, by @patrickhlauke.
-
Use connected keyword instead of removing a node w3c/pointerevents#267, by @NavidZ.
-
-
2 pull requests merged.
-
Initial draft charter for PE3 w3c/pointerevents#268.
-
Use connected keyword instead of removing a node w3c/pointerevents#267.
-
-
2 pull requests received 13 new comments.
-
Introduce pointerrawupdate to address the high frequency usecases w3c/pointerevents#260 (7 comments by @NavidZ, @smaug----)
-
Use connected keyword instead of removing a node w3c/pointerevents#267 (6 comments by @NavidZ, @patrickhlauke, @smaug----)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
Remove myself as editor and add NavidZ? w3c/pointerevents#263, by @RByers.
-
-
3 issues closed.
-
Concern about "InvalidPointerId" DOMException. w3c/pointerevents#256.
-
Same table style for CSS touch-action property? w3c/pointerevents#254.
-
Remove myself as editor and add NavidZ? w3c/pointerevents#263.
-
-
5 issues received 27 new comments.
-
Concern about "InvalidPointerId" DOMException. w3c/pointerevents#256 (11 comments by @NavidZ, @patrickhlauke, @scottgonzalez, @smaug----)
-
Remove myself as editor and add NavidZ? w3c/pointerevents#263 (9 comments by @mbrubeck, @NavidZ, @patrickhlauke, @RByers)
-
What should be the 'detail' property of pointer events? w3c/pointerevents#98 (3 comments by @my2iu, @NavidZ, @patrickhlauke)
-
"When the pointer capture target override is removed from its ownerDocument's tree" should talk about target not being connected anymore w3c/pointerevents#259 (3 comments by @patrickhlauke, @smaug----)
-
-
3 pull requests opened.
-
Change DOMException from InvalidPointerId to NotFoundError w3c/pointerevents#266, by @patrickhlauke.
-
Editorial: Add `<dfn>` to `touch-action` definition w3c/pointerevents#265, by @patrickhlauke.
-
-
3 pull requests merged.
-
Change DOMException from InvalidPointerId to NotFoundError w3c/pointerevents#266.
-
Editorial: Add `<dfn>` to `touch-action` definition w3c/pointerevents#265.
-
-
2 pull requests received 2 new comments.
-
Introduce pointerrawupdate to address the high frequency usecases w3c/pointerevents#260 (1 comment by @patrickhlauke)
-
Fix respec errors, minor editorial changes "for devices"/"for hardware", add Navid Zolghadr as co-editor w3c/pointerevents#264 (1 comment by @patrickhlauke)
-
GitHub
w3c/pointerevents
-
2 pull requests opened.
-
Add informative note about tangential pressure and Windows w3c/pointerevents#262, by @patrickhlauke.
-
pointerenter and pointerleave should not be composed w3c/pointerevents#261, by @smaug----.
-
-
1 pull request merged.
-
pointerenter and pointerleave should not be composed w3c/pointerevents#261.
-
-
1 pull request closed.
-
Add informative note about tangential pressure and Windows w3c/pointerevents#262.
-
-
2 pull requests received 6 new comments.
-
Add informative note about tangential pressure and Windows w3c/pointerevents#262 (4 comments by @NavidZ, @patrickhlauke, @plehegar)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
1 issue received 3 new comments.
-
Define a low latency event that isn't occur in the document lifecycle w3c/pointerevents#214 (3 comments by @NavidZ, @smaug----)
-
-
1 pull request opened.
-
Introduce pointerrawupdate to address the high frequency usecases w3c/pointerevents#260, by @NavidZ.
-
-
1 pull request received 8 new comments.
-
Introduce pointerrawupdate to address the high frequency usecases w3c/pointerevents#260 (8 comments by @NavidZ, @smaug----)
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Need clarification for when mouseenter/mouseleave should be dispatched for moved elements. w3c/pointerevents#611, by @flackr.
-
Concern about "InvalidPointerId" DOMException. w3c/pointerevents#256, by @yuki3.
-
-
1 issue closed.
-
Consider adding API to get predicted points w3c/pointerevents#38.
-
-
1 issue received 2 new comments.
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (2 comments by @garykac, @RByers)
-
-
2 pull requests opened.
-
Update web-platform-tests URLs w3c/pointerevents#258, by @foolip.
-
Propose a getPredictedEvents API with example w3c/pointerevents#257, by @NavidZ.
-
-
2 pull requests merged.
-
Propose a getPredictedEvents API with example w3c/pointerevents#257.
-
Update web-platform-tests URLs w3c/pointerevents#258.
-
-
2 pull requests received 2 new comments.
TR publications
-
2 documents published.
-
Pointer Events published twice as a Candidate Recommendation Snapshot. History of Pointer Events
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Security & Privacy Section Removed Between April 4, 2018 and May 10th, 2018 Drafts w3c/pointerevents#255, by @jasonanovak.
-
Same table style for CSS touch-action property? w3c/pointerevents#254, by @saschanaz.
-
-
1 issue closed.
-
Security & Privacy Section Removed Between April 4, 2018 and May 10th, 2018 Drafts w3c/pointerevents#255.
-
-
2 issues received 6 new comments.
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (3 comments by @garykac, @masayuki-nakano)
-
Security & Privacy Section Removed Between April 4, 2018 and May 10th, 2018 Drafts w3c/pointerevents#255 (3 comments by @patrickhlauke)
-
-
1 pull request opened.
-
GlobalEventHandlers is a mixin w3c/pointerevents#253, by @saschanaz.
-
-
1 pull request closed.
-
GlobalEventHandlers is a mixin w3c/pointerevents#253.
-
-
1 pull request received 2 new comments.
TR publications
-
1 document published.
-
Pointer Events published as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
3 issues opened.
-
Different mousedown behavior between Firefox and Chrome/Safari w3c/pointerevents#610, by @nuragic.
-
Need algorithm for how mouse click events are fired w3c/pointerevents#579, by @garykac.
-
Need algorithm for how mouse events are fired w3c/pointerevents#609, by @garykac.
-
-
10 issues closed.
-
PointerEvents should have fractional coordinates w3c/pointerevents#107.
-
What should be the width/height of touch pointerUp? w3c/pointerevents#225.
-
Determine when boundary events are fired after capture is released w3c/pointerevents#15.
-
Change the reference label for UI Events Specification w3c/pointerevents#60.
-
Should setPointerCapture work in Shadow DOM w3c/pointerevents#221.
-
It isn't clear what "page" means in "Setting Pointer Capture" w3c/pointerevents#220.
-
Should spec mention OS/UA features like palm rejection? w3c/pointerevents#165.
-
Clarify duration of pointer event suppression during a touch action w3c/pointerevents#118.
-
11 issues received 17 new comments.
-
Should spec defines what triggers pointerover and pointerenter when implicitly releasing pointer capture? w3c/pointerevents#173 (6 comments by @NavidZ, @patrickhlauke, @smaug----)
-
Need algorithm for how mouse click events are fired w3c/pointerevents#579 (2 comments by @domenic, @garykac)
-
What should be the width/height of touch pointerUp? w3c/pointerevents#225 (1 comment by @patrickhlauke)
-
Determine when boundary events are fired after capture is released w3c/pointerevents#15 (1 comment by @patrickhlauke)
-
Should "Setting Pointer Capture" with elements which are in document, but doesn't have associated browsering context w3c/pointerevents#219 (1 comment by @patrickhlauke)
-
-
7 pull requests opened.
-
Additional security/privacy clarifications following horizontal review w3c/pointerevents#252, by @patrickhlauke.
-
Add boundary events in implicit capture scenarios w3c/pointerevents#251, by @NavidZ.
-
Minor markup cleanup w3c/pointerevents#250, by @patrickhlauke.
-
Minor markup cleanup w3c/pointerevents#249, by @patrickhlauke.
-
Change reference from DOM-LEVEL-3-EVENTS to UIEVENTS w3c/pointerevents#248, by @patrickhlauke.
-
Replace "page" with "document" for clarity and harmonization with PointerLock w3c/pointerevents#247, by @patrickhlauke.
-
Replace prose about `ownerDocument` tree with DOM4 concept of `connected` w3c/pointerevents#246, by @patrickhlauke.
-
-
10 pull requests merged.
-
Add boundary events in implicit capture scenarios w3c/pointerevents#251.
-
Additional security/privacy clarifications following horizontal review w3c/pointerevents#252.
-
Move single directional touch-action values to the extension spec w3c/pointerevents#238.
-
Minor markup cleanup w3c/pointerevents#250.
-
Minor markup cleanup w3c/pointerevents#249.
-
Change reference from DOM-LEVEL-3-EVENTS to UIEVENTS w3c/pointerevents#248.
-
Replace prose about `ownerDocument` tree with DOM4 concept of `connected` w3c/pointerevents#246.
-
Replace "page" with "document" for clarity and harmonization with PointerLock w3c/pointerevents#247.
-
Add informative note about palm rejection w3c/pointerevents#244.
-
Add informative note about UA handling of "compound" gestures w3c/pointerevents#243.
-
-
5 pull requests received 17 new comments.
-
Replace prose about `ownerDocument` tree with DOM4 concept of `connected` w3c/pointerevents#246 (5 comments by @patrickhlauke, @smaug----)
-
Additional security/privacy clarifications following horizontal review w3c/pointerevents#252 (4 comments by @NavidZ, @patrickhlauke, @smaug----)
-
Add boundary events in implicit capture scenarios w3c/pointerevents#251 (4 comments by @mustaqahmed, @NavidZ, @patrickhlauke)
-
Move single directional touch-action values to the extension spec w3c/pointerevents#238 (2 comments by @NavidZ, @patrickhlauke)
-
Add informative note about UA handling of "compound" gestures w3c/pointerevents#243 (2 comments by @NavidZ, @patrickhlauke)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
Clarify that canceling pointerdown shouldn't affect to scrollbar handling w3c/pointerevents#236, by @smaug----.
-
-
10 issues closed.
-
ReSpec warning on "Privacy and Security" w3c/pointerevents#183.
-
Spec references both W3C DOM4 and WHATWG-DOM w3c/pointerevents#160.
-
Pointer events & disabled form elements w3c/pointerevents#177.
-
Can one active pointer cancel other pointers of different types? w3c/pointerevents#226.
-
Clarify that canceling pointerdown shouldn't affect to scrollbar handling w3c/pointerevents#236.
-
Simultaneously move / drag with multiple pointer devices w3c/pointerevents#570.
-
Behaviour of dblclicks is not specified w3c/pointerevents#171.
-
Should pointer capture work when element is in non-browsing-context w3c/pointerevents#172.
-
Would pointerType === 'pen' events participate in HTML5 Drag & Drop? w3c/pointerevents#212.
-
When to continue firing pointer events after a drag operation? w3c/pointerevents#222.
-
-
1 issue reopened.
-
Behavior of PointerEvent.fromElement/toElement w3c/pointerevents#167, by @mustaqahmed.
-
-
24 issues received 36 new comments.
-
Spec references both W3C DOM4 and WHATWG-DOM w3c/pointerevents#160 (5 comments by @NavidZ, @patrickhlauke)
-
Behavior of PointerEvent.fromElement/toElement w3c/pointerevents#167 (5 comments by @mustaqahmed, @NavidZ, @RByers)
-
setPointerCapture should be disabled in sandboxed iframes by default w3c/pointerevents#16 (2 comments by @NavidZ, @patrickhlauke)
-
Click event while a pointer event is captured w3c/pointerevents#75 (2 comments by @NavidZ, @smaug----)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (1 comment by @NavidZ)
-
Clarify duration of pointer event suppression during a touch action w3c/pointerevents#118 (1 comment by @NavidZ)
-
Could we ever do implicit capture for all pointer types? w3c/pointerevents#125 (1 comment by @NavidZ)
-
Clarify that canceling pointerdown shouldn't affect to scrollbar handling w3c/pointerevents#236 (1 comment by @NavidZ)
-
Simultaneously move / drag with multiple pointer devices w3c/pointerevents#570 (1 comment by @NavidZ)
-
Should spec mention OS/UA features like palm rejection? w3c/pointerevents#165 (1 comment by @NavidZ)
-
Should pointer capture work when element is in non-browsing-context w3c/pointerevents#172 (1 comment by @NavidZ)
-
Should spec defines what triggers pointerover and pointerenter when implicitly releasing pointer capture? w3c/pointerevents#173 (1 comment by @NavidZ)
-
Would pointerType === 'pen' events participate in HTML5 Drag & Drop? w3c/pointerevents#212 (1 comment by @NavidZ)
-
Should "Setting Pointer Capture" with elements which are in document, but doesn't have associated browsering context w3c/pointerevents#219 (1 comment by @NavidZ)
-
It isn't clear what "page" means in "Setting Pointer Capture" w3c/pointerevents#220 (1 comment by @NavidZ)
-
When to continue firing pointer events after a drag operation? w3c/pointerevents#222 (1 comment by @NavidZ)
-
-
12 pull requests opened.
-
Meta: fixing my borked fork w3c/pointerevents#245, by @patrickhlauke.
-
Add informative note about palm rejection w3c/pointerevents#244, by @patrickhlauke.
-
Add informative note about UA handling of "compound" gestures w3c/pointerevents#243, by @patrickhlauke.
-
Update revision history w3c/pointerevents#242, by @patrickhlauke.
-
Fix incorrect in-document link w3c/pointerevents#241, by @patrickhlauke.
-
Update WHATWG-DOM to DOM4 w3c/pointerevents#240, by @NavidZ.
-
Add missing thanks w3c/pointerevents#239, by @NavidZ.
-
Move single directional touch-action values to the extension spec w3c/pointerevents#238, by @NavidZ.
-
Remove local biblio entry w3c/pointerevents#237, by @EiraGe.
-
Add security and privacy considerations section w3c/pointerevents#235, by @patrickhlauke.
-
Added a note on null fromElement and toElement. w3c/pointerevents#234, by @mustaqahmed.
-
Add possibility of having multiple pointers canceled by user agents w3c/pointerevents#233, by @NavidZ.
-
-
9 pull requests merged.
-
Meta: fixing my borked fork w3c/pointerevents#245.
-
Update revision history w3c/pointerevents#242.
-
Fix incorrect in-document link w3c/pointerevents#241.
-
Add security and privacy considerations section w3c/pointerevents#235.
-
Update WHATWG-DOM to DOM4 w3c/pointerevents#240.
-
Add missing thanks w3c/pointerevents#239.
-
Remove local biblio entry w3c/pointerevents#237.
-
Add possibility of having multiple pointers canceled by user agents w3c/pointerevents#233.
-
Added a note on null fromElement and toElement. w3c/pointerevents#234.
-
-
1 pull request closed.
-
Add security/privacy considerations w3c/pointerevents#193.
-
-
10 pull requests received 24 new comments.
-
Add possibility of having multiple pointers canceled by user agents w3c/pointerevents#233 (6 comments by @mustaqahmed, @patrickhlauke)
-
Added a note on null fromElement and toElement. w3c/pointerevents#234 (3 comments by @mustaqahmed, @NavidZ)
-
Add informative note about UA handling of "compound" gestures w3c/pointerevents#243 (2 comments by @patrickhlauke)
-
Add security and privacy considerations section w3c/pointerevents#235 (2 comments by @NavidZ, @patrickhlauke)
-
Move single directional touch-action values to the extension spec w3c/pointerevents#238 (1 comment by @patrickhlauke)
-
TR publications
-
1 document published.
-
Pointer Events published as a Working Draft. History of Pointer Events
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
May the state of modifier keys influence MouseEvent.button? w3c/pointerevents#608, by @jfirebaugh.
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592, by @masayuki-nakano.
-
-
2 issues closed.
-
Touch/Trackpad finger position w3c/pointerevents#228.
-
-
1 issue reopened.
-
Should setPointerCapture work in Shadow DOM w3c/pointerevents#221, by @smaug----.
-
-
12 issues received 23 new comments.
-
Should setPointerCapture work in Shadow DOM w3c/pointerevents#221 (6 comments by @mustaqahmed, @patrickhlauke, @smaug----)
-
setPointerCapture should be disabled in sandboxed iframes by default w3c/pointerevents#16 (4 comments by @NavidZ, @patrickhlauke, @RByers)
-
PointerEvents should have fractional coordinates w3c/pointerevents#107 (3 comments by @NavidZ, @patrickhlauke, @RByers)
-
Behaviour of dblclicks is not specified w3c/pointerevents#171 (2 comments by @NavidZ, @patrickhlauke)
-
May the state of modifier keys influence MouseEvent.button? w3c/pointerevents#608 (1 comment by @garykac)
-
Stylus eraser: should it be a new pointerType instead of a button state? w3c/pointerevents#134 (1 comment by @patrickhlauke)
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (1 comment by @masayuki-nakano)
-
Should the spec defines how to handle when the pen's left button and the pen tip both are pressed? w3c/pointerevents#207 (1 comment by @patrickhlauke)
-
Difficulty understanding getCoalescedEvents definition w3c/pointerevents#215 (1 comment by @patrickhlauke)
-
-
2 pull requests opened.
-
missing / in closing element w3c/pointerevents#232, by @plehegar.
-
Tweaks in respec config and fixing data-lt attributes w3c/pointerevents#231, by @plehegar.
-
-
2 pull requests merged.
-
missing / in closing element w3c/pointerevents#232.
-
Tweaks in respec config and fixing data-lt attributes w3c/pointerevents#231.
-
-
1 pull request received 1 new comment.
-
Tweaks in respec config and fixing data-lt attributes w3c/pointerevents#231 (1 comment by @patrickhlauke)
-
GitHub
w3c/pointerevents
-
2 issues received 2 new comments.
-
What should be the width/height of touch pointerUp? w3c/pointerevents#225 (1 comment by @mustaqahmed)