Pointer Events Working Group - Activity in 2016
No matches.
GitHub
w3c/pointerevents
-
7 issues opened.
-
Should spec mention OS/UA features like palm rejection? w3c/pointerevents#165, by @patrickhlauke.
-
Simultaneously move / drag with multiple pointer devices w3c/pointerevents#570, by @mingchou.
-
New respec warnings about missing dfns w3c/pointerevents#163, by @RByers.
-
Would be good to better clarify pointer event firing w3c/pointerevents#569, by @bzbarsky.
-
Spec references both W3C DOM4 and WHATWG-DOM w3c/pointerevents#160, by @RByers.
-
Touch-action should distinguish between single- vs multi-finger panning w3c/pointerevents#159, by @mustaqahmed.
-
Should on(got/lost)pointercapture be in GlobalEventHandlers? w3c/pointerevents#157, by @NavidZ.
-
-
5 issues closed.
-
Add explicit control over pinch-zoom to touch-action w3c/pointerevents#565.
-
Define ordering of lostpointercapture and pointerout/leave for touch w3c/pointerevents#142.
-
Should on(got/lost)pointercapture be in GlobalEventHandlers? w3c/pointerevents#157.
-
Fire pointerover/enter before gotpointercapture w3c/pointerevents#156.
-
Need to clarify what triggers boundary events when releasing a capture w3c/pointerevents#145.
-
-
2 issues reopened.
-
Define ordering of lostpointercapture and pointerout/leave for touch w3c/pointerevents#142, by @mustaqahmed.
-
Should on(got/lost)pointercapture be in GlobalEventHandlers? w3c/pointerevents#157, by @RByers.
-
-
8 issues received 35 new comments.
-
Spec references both W3C DOM4 and WHATWG-DOM w3c/pointerevents#160 (3 comments by @chaals, @patrickhlauke, @RByers)
-
Add explicit control over pinch-zoom to touch-action w3c/pointerevents#565 (3 comments by @patrickhlauke, @RByers)
-
Simultaneously move / drag with multiple pointer devices w3c/pointerevents#570 (3 comments by @mingchou, @patrickhlauke)
-
Touch-action should distinguish between single- vs multi-finger panning w3c/pointerevents#159 (2 comments by @lpd-au, @patrickhlauke)
-
Define ordering of lostpointercapture and pointerout/leave for touch w3c/pointerevents#142 (1 comment by @mustaqahmed)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (1 comment by @RByers)
-
2 pull requests opened.
-
Reference compat spec touch-action entry w3c/pointerevents#162, by @RByers.
-
Move ongot/lostpointercapture to GlobalEventHandlers w3c/pointerevents#158, by @NavidZ.
-
-
2 pull requests merged.
-
Reference compat spec touch-action entry w3c/pointerevents#162.
-
Move ongot/lostpointercapture to GlobalEventHandlers w3c/pointerevents#158.
-
-
2 pull requests received 5 new comments.
-
Reference compat spec touch-action entry w3c/pointerevents#162 (3 comments by @dtapuska, @RByers, @smaug----)
-
Move ongot/lostpointercapture to GlobalEventHandlers w3c/pointerevents#158 (2 comments by @RByers, @teddink)
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Fire pointerover/enter before gotpointercapture w3c/pointerevents#156, by @NavidZ.
-
-
3 issues closed.
-
How should touch-action behave for span? w3c/pointerevents#150.
-
pointerup pressure should always be 0 w3c/pointerevents#146.
-
Update tap event order list for single logical mouse pointer w3c/pointerevents#117.
-
-
1 issue reopened.
-
Need to clarify what triggers boundary events when releasing a capture w3c/pointerevents#145, by @RByers.
-
-
7 issues received 19 new comments.
-
pointerType: 'dial' w3c/pointerevents#152 (11 comments by @appsforartists, @dtapuska, @lpd-au, @mustaqahmed, @patrickhlauke, @shepazu)
-
WheelEvent.intDelta(X|Y|Z) might be useful for some web apps which cannot scroll its contents smoothly w3c/pointerevents#589 (2 comments by @masayuki-nakano, @smaug----)
-
Need to clarify what triggers boundary events when releasing a capture w3c/pointerevents#145 (1 comment by @NavidZ)
-
Could we ever do implicit capture for all pointer types? w3c/pointerevents#125 (1 comment by @patrickhlauke)
-
-
3 pull requests opened.
-
Add extension doc link to readme w3c/pointerevents#155, by @NavidZ.
-
Clarify the hit test and capturing target for boundary events w3c/pointerevents#154, by @NavidZ.
-
Call out pressure=0 for pointerup events w3c/pointerevents#153, by @NavidZ.
-
-
5 pull requests merged.
-
Add extension doc link to readme w3c/pointerevents#155.
-
Initial draft of getCoalescedEvents API w3c/pointerevents#149.
-
Clarify the hit test and capturing target for boundary events w3c/pointerevents#154.
-
Call out pressure=0 for pointerup events w3c/pointerevents#153.
-
Legacy mouse event: fixed a missing text & a note w3c/pointerevents#151.
-
-
6 pull requests received 51 new comments.
-
Initial draft of getCoalescedEvents API w3c/pointerevents#149 (38 comments by @mustaqahmed, @NavidZ, @patrickhlauke, @RByers)
-
Clarify the hit test and capturing target for boundary events w3c/pointerevents#154 (5 comments by @NavidZ, @patrickhlauke, @RByers, @teddink)
-
Call out pressure=0 for pointerup events w3c/pointerevents#153 (4 comments by @NavidZ, @patrickhlauke, @scottgonzalez)
-
Legacy mouse event: fixed a missing text & a note w3c/pointerevents#151 (1 comment by @patrickhlauke)
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
pointerType: 'dial' w3c/pointerevents#152, by @appsforartists.
-
How should touch-action behave for span? w3c/pointerevents#150, by @NavidZ.
-
-
5 issues closed.
-
When are lost/gotpointercapture delayed until the next pointer event? w3c/pointerevents#32.
-
Incorrect order of the events in process pending pointer capture section w3c/pointerevents#39.
-
What should be the 'detail' property of pointer events? w3c/pointerevents#98.
-
Should pressure be set to 1 or .5 on devices that don't report it? w3c/pointerevents#147.
-
-
1 issue reopened.
-
Could we ever do implicit capture for all pointer types? w3c/pointerevents#125, by @RByers.
-
-
14 issues received 28 new comments.
-
Could we ever do implicit capture for all pointer types? w3c/pointerevents#125 (5 comments by @mustaqahmed, @NavidZ, @patrickhlauke, @RByers, @scottgonzalez)
-
Should pressure be set to 1 or .5 on devices that don't report it? w3c/pointerevents#147 (5 comments by @appsforartists, @dfleck, @mustaqahmed)
-
Define ordering of lostpointercapture and pointerout/leave for touch w3c/pointerevents#142 (2 comments by @NavidZ, @teddink)
-
How should touch-action behave for span? w3c/pointerevents#150 (2 comments by @mustaqahmed, @NavidZ)
-
When are lost/gotpointercapture delayed until the next pointer event? w3c/pointerevents#32 (1 comment by @NavidZ)
-
While pointer is captured the boundary of the capturing element should be itself and all its children w3c/pointerevents#62 (1 comment by @NavidZ)
-
Update tap event order list for single logical mouse pointer w3c/pointerevents#117 (1 comment by @NavidZ)
-
Incorrect order of the events in process pending pointer capture section w3c/pointerevents#39 (1 comment by @NavidZ)
-
Need to clarify what triggers boundary events when releasing a capture w3c/pointerevents#145 (1 comment by @NavidZ)
-
-
2 pull requests opened.
-
Legacy mouse event: fixed a missing text & a note w3c/pointerevents#151, by @mustaqahmed.
-
Initial draft of getCoalescedEvents API w3c/pointerevents#149, by @NavidZ.
-
-
2 pull requests received 16 new comments.
-
Initial draft of getCoalescedEvents API w3c/pointerevents#149 (10 comments by @mustaqahmed, @NavidZ, @scottgonzalez)
-
Legacy mouse event: fixed a missing text & a note w3c/pointerevents#151 (6 comments by @mustaqahmed, @patrickhlauke, @RByers)
-
GitHub
w3c/pointerevents
-
10 issues opened.
-
Reduce scroll performance impact of `wheel` listeners w3c/pointerevents#588, by @RByers.
-
Update tests for reduce-hit-tests changes w3c/pointerevents#148, by @RByers.
-
Should pressure be set to 1 or .5 on devices that don't report it? w3c/pointerevents#147, by @appsforartists.
-
pointerup pressure should always be 0 w3c/pointerevents#146, by @appsforartists.
-
Need to clarify what triggers boundary events when releasing a capture w3c/pointerevents#145, by @mustaqahmed.
-
Consider having explicit capture (sometimes) include boundary events w3c/pointerevents#143, by @RByers.
-
Define ordering of lostpointercapture and pointerout/leave for touch w3c/pointerevents#142, by @RByers.
-
Add attribute tests for nohover pointer events like touch w3c/pointerevents#568, by @NavidZ.
-
Need a test for releasing pointer capture while element.hasPointerCapture is false w3c/pointerevents#140, by @NavidZ.
-
Some tests don't work properly with mobile-sized viewports w3c/pointerevents#139, by @RByers.
-
-
6 issues closed.
-
Update tests for reduce-hit-tests changes w3c/pointerevents#148.
-
Should a captured pointer send boundary events by default? w3c/pointerevents#566.
-
Pointermove should not require a hit-test by default for touch w3c/pointerevents#8.
-
Add attribute tests for nohover pointer events like touch w3c/pointerevents#568.
-
Touch-action isn't flexible enough for direction-specific behavior w3c/pointerevents#6.
-
Need a test for releasing pointer capture while element.hasPointerCapture is false w3c/pointerevents#140.
-
-
10 issues received 52 new comments.
-
Should pressure be set to 1 or .5 on devices that don't report it? w3c/pointerevents#147 (25 comments by @appsforartists, @cynthia, @dfleck, @mustaqahmed, @NavidZ, @patrickhlauke, @RByers, @teddink)
-
pointerup pressure should always be 0 w3c/pointerevents#146 (8 comments by @appsforartists, @dfleck, @mustaqahmed, @NavidZ)
-
Add explicit control over pinch-zoom to touch-action w3c/pointerevents#565 (4 comments by @RByers, @staktrace, @teddink)
-
Stylus eraser: should it be a new pointerType instead of a button state? w3c/pointerevents#134 (4 comments by @dfleck, @mustaqahmed, @patrickhlauke)
-
Consider having explicit capture (sometimes) include boundary events w3c/pointerevents#143 (3 comments by @NavidZ, @RByers, @scottgonzalez)
-
Need to clarify what triggers boundary events when releasing a capture w3c/pointerevents#145 (2 comments by @NavidZ, @RByers)
-
Define ordering of lostpointercapture and pointerout/leave for touch w3c/pointerevents#142 (2 comments by @NavidZ, @teddink)
-
Should a captured pointer send boundary events by default? w3c/pointerevents#566 (1 comment by @RByers)
-
Touch-action isn't flexible enough for direction-specific behavior w3c/pointerevents#6 (1 comment by @RByers)
-
-
1 pull request opened.
-
Reduce hit tests w3c/pointerevents#144, by @RByers.
-
-
2 pull requests merged.
-
Reduce hit tests w3c/pointerevents#144.
-
Remove boundary events and use capture node as target w3c/pointerevents#138.
-
-
1 pull request received 9 new comments.
-
Remove boundary events and use capture node as target w3c/pointerevents#138 (9 comments by @mustaqahmed, @NavidZ, @RByers)
-
Participants
-
1 participant joined.
-
Doug Schepers (W3C) joined.
-
GitHub
w3c/pointerevents
-
7 issues opened.
-
releasePointerCapture right after setPointerCapture is no-op w3c/pointerevents#136, by @smaug----.
-
What is the relationship between setPointerCapture, PointerLock, and browser default behaviors? w3c/pointerevents#135, by @mingchou.
-
Stylus eraser: should it be a new pointerType instead of a button state? w3c/pointerevents#134, by @mustaqahmed.
-
Should Element.hasPointerCapture return true or false in the listener of pointerup or pointercancel? w3c/pointerevents#132, by @mingchou.
-
Incorrect movementX/Y in PointerEvents w3c/pointerevents#567, by @NavidZ.
-
How best to inflate hit targets for touch? w3c/pointerevents#126, by @RByers.
-
-
6 issues closed.
-
releasePointerCapture right after setPointerCapture is no-op w3c/pointerevents#136.
-
Attributes of lost/gotpointercapture events fired immediately on set/release capture w3c/pointerevents#113.
-
Add feature detection section w3c/pointerevents#94.
-
Add Element.hasPointerCapture API w3c/pointerevents#121.
-
-
9 issues received 34 new comments.
-
Stylus eraser: should it be a new pointerType instead of a button state? w3c/pointerevents#134 (13 comments by @mustaqahmed, @patrickhlauke, @RByers, @scottgonzalez)
-
When are lost/gotpointercapture delayed until the next pointer event? w3c/pointerevents#32 (5 comments by @mingchou, @NavidZ, @smaug----, @teddink)
-
Should Element.hasPointerCapture return true when set pointer capture to another element and release it immediately? w3c/pointerevents#133 (4 comments by @mingchou, @mustaqahmed, @NavidZ)
-
Incorrect movementX/Y in PointerEvents w3c/pointerevents#567 (3 comments by @patrickhlauke, @RByers, @scheib)
-
Should Element.hasPointerCapture return true or false in the listener of pointerup or pointercancel? w3c/pointerevents#132 (3 comments by @mingchou, @mustaqahmed, @NavidZ)
-
Pointermove should not require a hit-test by default for touch w3c/pointerevents#8 (2 comments by @RByers)
-
How best to inflate hit targets for touch? w3c/pointerevents#126 (2 comments by @patrickhlauke, @RByers)
-
What is the relationship between setPointerCapture, PointerLock, and browser default behaviors? w3c/pointerevents#135 (1 comment by @RByers)
-
-
6 pull requests opened.
-
Remove boundary events and use capture node as target w3c/pointerevents#138, by @NavidZ.
-
Fix the wording in releasePointerCapture to use hasPointerCapture w3c/pointerevents#137, by @NavidZ.
-
add feature detection example, clean up code examples w3c/pointerevents#130, by @patrickhlauke.
-
Add initial implicit capture proposal w3c/pointerevents#129, by @RByers.
-
Cleanup event definitions for easier linking w3c/pointerevents#128, by @RByers.
-
Add hasPointerCapture w3c/pointerevents#127, by @RByers.
-
-
6 pull requests merged.
-
Fix the wording in releasePointerCapture to use hasPointerCapture w3c/pointerevents#137.
-
got/lostpointercapture events: attributes and immediate firing on implicit release w3c/pointerevents#122.
-
Add initial implicit capture proposal w3c/pointerevents#129.
-
add feature detection example, clean up code examples w3c/pointerevents#130.
-
Add hasPointerCapture w3c/pointerevents#127.
-
Cleanup event definitions for easier linking w3c/pointerevents#128.
-
-
6 pull requests received 47 new comments.
-
got/lostpointercapture events: attributes and immediate firing on implicit release w3c/pointerevents#122 (15 comments by @mustaqahmed, @NavidZ, @RByers)
-
Add hasPointerCapture w3c/pointerevents#127 (14 comments by @patrickhlauke, @RByers, @scottgonzalez)
-
add feature detection example, clean up code examples w3c/pointerevents#130 (7 comments by @NavidZ, @patrickhlauke, @RByers, @teddink)
-
Add initial implicit capture proposal w3c/pointerevents#129 (6 comments by @NavidZ, @patrickhlauke, @RByers, @scottgonzalez)
-
Fix the wording in releasePointerCapture to use hasPointerCapture w3c/pointerevents#137 (3 comments by @mustaqahmed, @patrickhlauke, @smaug----)
-
Cleanup event definitions for easier linking w3c/pointerevents#128 (2 comments by @patrickhlauke, @RByers)
-
TR publications
-
1 document published.
-
Pointer Events - Level 2 published as a First Public Working Draft. History of Pointer Events - Level 2
-
GitHub
w3c/pointerevents
-
18 issues opened.
-
Could we ever do implicit capture for all pointer types? w3c/pointerevents#125, by @RByers.
-
How to determine when a tap is impossible w3c/pointerevents#124, by @RByers.
-
Standardize CSS pseudoclass behavior for touch w3c/pointerevents#123, by @RByers.
-
Add Element.hasPointerCapture API w3c/pointerevents#121, by @RByers.
-
Explore unifying web-platform-test automation logic w3c/pointerevents#120, by @RByers.
-
Clarify duration of pointer event suppression during a touch action w3c/pointerevents#118, by @RByers.
-
Update tap event order list for single logical mouse pointer w3c/pointerevents#117, by @RByers.
-
Clarify what touch-action allows with rotated scrollable elements w3c/pointerevents#115, by @staktrace.
-
Attributes of lost/gotpointercapture events fired immediately on set/release capture w3c/pointerevents#113, by @mustaqahmed.
-
Red text on dark blue background hard to see w3c/pointerevents#112, by @DavidMacDonald.
-
typo w3c/pointerevents#111, by @DavidMacDonald.
-
typo w3c/pointerevents#109, by @DavidMacDonald.
-
PointerEvents should have fractional coordinates w3c/pointerevents#107, by @mustaqahmed.
-
Should DragEvent be upgraded to a PointerEvent? w3c/pointerevents#106, by @RByers.
-
Current draft: the definitions of tiltY and twist are "hidden"! w3c/pointerevents#103, by @mustaqahmed.
-
Current draft: the definitions of tiltY and twist is not visible" w3c/pointerevents#102, by @mustaqahmed.
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100, by @RByers.
-
What should be the 'detail' property of pointer events? w3c/pointerevents#98, by @NavidZ.
-
-
9 issues closed.
-
Mouse Event compatibility model for touch is incompatible with current practice w3c/pointerevents#7.
-
Red text on dark blue background hard to see w3c/pointerevents#112.
-
typo w3c/pointerevents#111.
-
typo w3c/pointerevents#109.
-
Support hovering button states w3c/pointerevents#14.
-
Convert spec IDL to "contiguous" style w3c/pointerevents#58.
-
Current draft: the definitions of tiltY and twist are "hidden"! w3c/pointerevents#103.
-
Current draft: the definitions of tiltY and twist is not visible" w3c/pointerevents#102.
-
Clarify click event firing for chorded buttons w3c/pointerevents#93.
-
-
2 issues reopened.
-
What should be the 'detail' property of pointer events? w3c/pointerevents#98, by @RByers.
-
Should a captured pointer send boundary events by default? w3c/pointerevents#566, by @teddink.
-
-
25 issues received 102 new comments.
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (14 comments by @dtapuska, @jacobrossi, @mustaqahmed, @NekR, @patrickhlauke, @RByers, @smaug----)
-
What should be the 'detail' property of pointer events? w3c/pointerevents#98 (13 comments by @NavidZ, @patrickhlauke, @RByers, @teddink)
-
Pointermove should not require a hit-test by default for touch w3c/pointerevents#8 (8 comments by @patrickhlauke, @RByers, @scottgonzalez, @teddink)
-
Clarify what touch-action allows with rotated scrollable elements w3c/pointerevents#115 (7 comments by @patrickhlauke, @RByers, @staktrace)
-
When are lost/gotpointercapture delayed until the next pointer event? w3c/pointerevents#32 (7 comments by @NavidZ, @RByers, @teddink)
-
PointerEvents should have fractional coordinates w3c/pointerevents#107 (6 comments by @patrickhlauke, @RByers, @scottgonzalez, @staktrace, @teddink)
-
Add explicit control over pinch-zoom to touch-action w3c/pointerevents#565 (6 comments by @RByers, @scottgonzalez, @teddink)
-
Could we ever do implicit capture for all pointer types? w3c/pointerevents#125 (5 comments by @patrickhlauke, @RByers, @teddink)
-
Add Element.hasPointerCapture API w3c/pointerevents#121 (4 comments by @NavidZ, @RByers, @scottgonzalez)
-
Attributes of lost/gotpointercapture events fired immediately on set/release capture w3c/pointerevents#113 (4 comments by @NavidZ, @RByers, @teddink)
-
Touch-action isn't flexible enough for direction-specific behavior w3c/pointerevents#6 (3 comments by @RByers)
-
illustration for "twist" ? w3c/pointerevents#88 (3 comments by @jacobrossi, @patrickhlauke, @teddink)
-
Compatibility mouse transition events should reflect a single logical mouse pointer w3c/pointerevents#35 (3 comments by @mustaqahmed, @patrickhlauke, @RByers)
-
Clarify click event firing for chorded buttons w3c/pointerevents#93 (3 comments by @RByers, @teddink)
-
Clarify duration of pointer event suppression during a touch action w3c/pointerevents#118 (2 comments by @RByers)
-
Red text on dark blue background hard to see w3c/pointerevents#112 (2 comments by @patrickhlauke, @scottgonzalez)
-
Should DragEvent be upgraded to a PointerEvent? w3c/pointerevents#106 (2 comments by @RByers, @smaug----)
-
Mouse Event compatibility model for touch is incompatible with current practice w3c/pointerevents#7 (2 comments by @RByers)
-
Should a captured pointer send boundary events by default? w3c/pointerevents#566 (2 comments by @teddink)
-
Update tap event order list for single logical mouse pointer w3c/pointerevents#117 (1 comment by @patrickhlauke)
-
Current draft: the definitions of tiltY and twist are "hidden"! w3c/pointerevents#103 (1 comment by @mustaqahmed)
-
Current draft: the definitions of tiltY and twist is not visible" w3c/pointerevents#102 (1 comment by @patrickhlauke)
-
setPointerCapture should be disabled in sandboxed iframes by default w3c/pointerevents#16 (1 comment by @RByers)
-
-
10 pull requests opened.
-
got/lostpointercapture events: attributes and immediate firing on implicit release w3c/pointerevents#122, by @NavidZ.
-
Reference TouchEvents spec for compat mouse events w3c/pointerevents#119, by @NavidZ.
-
Add detail=0 for pointerevents w3c/pointerevents#116, by @NavidZ.
-
update abstract/sotd w3c/pointerevents#114, by @patrickhlauke.
-
typo w3c/pointerevents#110, by @patrickhlauke.
-
fixing typo w3c/pointerevents#108, by @dret.
-
Update revision history w3c/pointerevents#105, by @patrickhlauke.
-
Fix broken WebIDL <dl> w3c/pointerevents#104, by @patrickhlauke.
-
convert deprecated <dl> based WebIDL to Contiguous IDL w3c/pointerevents#101, by @patrickhlauke.
-
Add pinch-zoom token to touch-action w3c/pointerevents#99, by @RByers.
-
-
9 pull requests merged.
-
Reference TouchEvents spec for compat mouse events w3c/pointerevents#119.
-
Add detail=0 for pointerevents w3c/pointerevents#116.
-
update abstract/sotd w3c/pointerevents#114.
-
typo w3c/pointerevents#110.
-
fixing typo w3c/pointerevents#108.
-
Update revision history w3c/pointerevents#105.
-
Removed "pen contact" condition on button/buttons. w3c/pointerevents#96.
-
convert deprecated <dl> based WebIDL to Contiguous IDL w3c/pointerevents#101.
-
Fix broken WebIDL <dl> w3c/pointerevents#104.
-
-
3 pull requests closed.
-
Reorder the events in process pending pointer capture w3c/pointerevents#40.
-
Clarified definition of capturing element borders w3c/pointerevents#63.
-
A possible immediate pointer capture processing w3c/pointerevents#76.
-
-
13 pull requests received 50 new comments.
-
got/lostpointercapture events: attributes and immediate firing on implicit release w3c/pointerevents#122 (11 comments by @NavidZ, @patrickhlauke, @RByers)
-
Removed "pen contact" condition on button/buttons. w3c/pointerevents#96 (8 comments by @mustaqahmed, @patrickhlauke, @RByers)
-
A possible immediate pointer capture processing w3c/pointerevents#76 (7 comments by @mustaqahmed, @NavidZ, @teddink)
-
Reference TouchEvents spec for compat mouse events w3c/pointerevents#119 (5 comments by @NavidZ, @patrickhlauke, @RByers)
-
Reorder the events in process pending pointer capture w3c/pointerevents#40 (3 comments by @mingchou, @NavidZ)
-
convert deprecated <dl> based WebIDL to Contiguous IDL w3c/pointerevents#101 (3 comments by @patrickhlauke, @RByers)
-
GitHub
w3c/pointerevents
-
11 issues opened.
-
strange/interesting results for Wacom Intuos Pro hovering clicks w3c/pointerevents#97, by @patrickhlauke.
-
Add feature detection section w3c/pointerevents#94, by @RByers.
-
Clarify click event firing for chorded buttons w3c/pointerevents#93, by @mustaqahmed.
-
Support Event.composed in Pointer Events w3c/pointerevents#91, by @hayatoito.
-
repo cleanup? w3c/pointerevents#90, by @patrickhlauke.
-
illustration for "twist" ? w3c/pointerevents#88, by @patrickhlauke.
-
"Pointer Event Types" misleading/inappropriate section heading? w3c/pointerevents#86, by @patrickhlauke.
-
Moving "Firing events..." and "Process Pending Pointer Capture" w3c/pointerevents#85, by @patrickhlauke.
-
tabs vs spaces (sorry) w3c/pointerevents#82, by @patrickhlauke.
-
Click event while a pointer event is captured w3c/pointerevents#75, by @NavidZ.
-
Preparation for FPWD publication of Pointer Events Level 2 w3c/pointerevents#73, by @patrickhlauke.
-
-
13 issues closed.
-
Support Event.composed in Pointer Events w3c/pointerevents#91.
-
strange/interesting results for Wacom Intuos Pro hovering clicks w3c/pointerevents#97.
-
repo cleanup? w3c/pointerevents#90.
-
Respec's "Latest published version" w3c/pointerevents#46.
-
"Pointer Event Types" misleading/inappropriate section heading? w3c/pointerevents#86.
-
Moving "Firing events..." and "Process Pending Pointer Capture" w3c/pointerevents#85.
-
Add additional digitizer/pen attributes: barrel pressure (tangential pressure) w3c/pointerevents#70.
-
Compatibility mouse transition events should reflect a single logical mouse pointer w3c/pointerevents#35.
-
tabs vs spaces (sorry) w3c/pointerevents#82.
-
Preparation for FPWD publication of Pointer Events Level 2 w3c/pointerevents#73.
-
Add additional digitizer/pen attributes: twist (rotation) w3c/pointerevents#25.
-
Should pointer IDs be unique even across different top-level browsing contexts? w3c/pointerevents#59.
-
ReSpec error: "A custom SotD paragraph is required for your type of document." w3c/pointerevents#71.
-
-
1 issue reopened.
-
Add feature detection section w3c/pointerevents#94, by @patrickhlauke.
-
-
24 issues received 73 new comments.
-
Click event while a pointer event is captured w3c/pointerevents#75 (14 comments by @mustaqahmed, @NavidZ, @RByers, @scottgonzalez, @teddink)
-
Add feature detection section w3c/pointerevents#94 (7 comments by @NekR, @patrickhlauke, @RByers, @teddink)
-
Support hovering button states w3c/pointerevents#14 (5 comments by @mustaqahmed, @RByers, @scottgonzalez)
-
Add explicit control over pinch-zoom to touch-action w3c/pointerevents#565 (5 comments by @pguerrant, @RByers, @staktrace)
-
Should a captured pointer send boundary events by default? w3c/pointerevents#566 (5 comments by @RByers, @scottgonzalez, @teddink)
-
When are lost/gotpointercapture delayed until the next pointer event? w3c/pointerevents#32 (4 comments by @NavidZ, @teddink)
-
ReSpec error: "A custom SotD paragraph is required for your type of document." w3c/pointerevents#71 (4 comments by @patrickhlauke, @RByers, @teddink)
-
strange/interesting results for Wacom Intuos Pro hovering clicks w3c/pointerevents#97 (3 comments by @dfleck, @patrickhlauke)
-
Clarify click event firing for chorded buttons w3c/pointerevents#93 (3 comments by @mustaqahmed, @patrickhlauke, @RByers)
-
Compatibility mouse transition events should reflect a single logical mouse pointer w3c/pointerevents#35 (2 comments by @mustaqahmed)
-
Support Event.composed in Pointer Events w3c/pointerevents#91 (2 comments by @hayatoito, @patrickhlauke)
-
"Pointer Event Types" misleading/inappropriate section heading? w3c/pointerevents#86 (2 comments by @patrickhlauke, @RByers)
-
Preparation for FPWD publication of Pointer Events Level 2 w3c/pointerevents#73 (2 comments by @patrickhlauke)
-
Touch-action isn't flexible enough for direction-specific behavior w3c/pointerevents#6 (1 comment by @scottgonzalez)
-
setPointerCapture should be disabled in sandboxed iframes by default w3c/pointerevents#16 (1 comment by @RByers)
-
Moving "Firing events..." and "Process Pending Pointer Capture" w3c/pointerevents#85 (1 comment by @RByers)
-
Add additional digitizer/pen attributes: barrel pressure (tangential pressure) w3c/pointerevents#70 (1 comment by @RByers)
-
Should pointer IDs be unique even across different top-level browsing contexts? w3c/pointerevents#59 (1 comment by @RByers)
-
-
15 pull requests opened.
-
Removed "pen contact" condition on button/buttons. w3c/pointerevents#96, by @mustaqahmed.
-
Repo cleanup w3c/pointerevents#95, by @patrickhlauke.
-
Fix #91. Make all pointer events composed events w3c/pointerevents#92, by @hayatoito.
-
Reorganize heading structure w3c/pointerevents#89, by @patrickhlauke.
-
Add digitizer/pen tangential (barrel) pressure w3c/pointerevents#87, by @patrickhlauke.
-
Markup cleanup (tabs vs spaces, indentation, validation errors) w3c/pointerevents#84, by @patrickhlauke.
-
Update revision history and shortname w3c/pointerevents#83, by @patrickhlauke.
-
Add the note to define the scope of pointerId more precisely w3c/pointerevents#81, by @NavidZ.
-
Add digitizer/pen tangential (barrel) pressure w3c/pointerevents#80, by @patrickhlauke.
-
Add digitizer/pen twist w3c/pointerevents#79, by @patrickhlauke.
-
Minor typo - missing "of" w3c/pointerevents#78, by @patrickhlauke.
-
Tweak SotD w3c/pointerevents#77, by @patrickhlauke.
-
A possible immediate pointer capture processing w3c/pointerevents#76, by @NavidZ.
-
Reintroduce the SotD w3c/pointerevents#74, by @patrickhlauke.
-
Update revision history w3c/pointerevents#72, by @patrickhlauke.
-
-
12 pull requests merged.
-
Fix #91. Make all pointer events composed events w3c/pointerevents#92.
-
Repo cleanup w3c/pointerevents#95.
-
Reorganize heading structure w3c/pointerevents#89.
-
Add digitizer/pen tangential (barrel) pressure w3c/pointerevents#87.
-
Markup cleanup (tabs vs spaces, indentation, validation errors) w3c/pointerevents#84.
-
Update revision history and shortname w3c/pointerevents#83.
-
Add digitizer/pen twist w3c/pointerevents#79.
-
Add the note to define the scope of pointerId more precisely w3c/pointerevents#81.
-
Minor typo - missing "of" w3c/pointerevents#78.
-
Tweak SotD w3c/pointerevents#77.
-
Reintroduce the SotD w3c/pointerevents#74.
-
Update revision history w3c/pointerevents#72.
-
-
1 pull request closed.
-
Add digitizer/pen tangential (barrel) pressure w3c/pointerevents#80.
-
-
11 pull requests received 55 new comments.
-
Removed "pen contact" condition on button/buttons. w3c/pointerevents#96 (14 comments by @mustaqahmed, @patrickhlauke, @scottgonzalez)
-
Add digitizer/pen tangential (barrel) pressure w3c/pointerevents#80 (10 comments by @patrickhlauke, @RByers, @teddink)
-
Fix #91. Make all pointer events composed events w3c/pointerevents#92 (8 comments by @hayatoito, @patrickhlauke, @RByers)
-
Markup cleanup (tabs vs spaces, indentation, validation errors) w3c/pointerevents#84 (4 comments by @patrickhlauke, @RByers)
-
Reorder the events in process pending pointer capture w3c/pointerevents#40 (3 comments by @NavidZ, @patrickhlauke)
-
Add the note to define the scope of pointerId more precisely w3c/pointerevents#81 (3 comments by @patrickhlauke, @RByers, @teddink)
-
A possible immediate pointer capture processing w3c/pointerevents#76 (2 comments by @NavidZ, @teddink)
-
Participants
-
2 organizations joined.
-
Microsoft Corporation joined.
-
Google LLC joined.
-
GitHub
w3c/pointerevents
-
6 issues opened.
-
ReSpec error: "A custom SotD paragraph is required for your type of document." w3c/pointerevents#71, by @RByers.
-
Add additional digitizer/pen attributes: barrel pressure (tangential pressure) w3c/pointerevents#70, by @patrickhlauke.
-
Default width/height attribute for mouse w3c/pointerevents#65, by @NavidZ.
-
How removing target in pointer event handler affects compat mouse event target w3c/pointerevents#64, by @NavidZ.
-
While pointer is captured the boundary of the capturing element should be itself and all its children w3c/pointerevents#62, by @NavidZ.
-
Should a captured pointer send boundary events by default? w3c/pointerevents#566, by @RByers.
-
-
9 issues closed.
-
Only people with push access can have issues assigned to them w3c/pointerevents#55.
-
Default width/height attribute for mouse w3c/pointerevents#65.
-
Configure this repo to use gitbot and the #pointerevents channel w3c/pointerevents#11.
-
Add 3D Mice w3c/pointerevents#26.
-
Should the spec really reference tracker anymore? w3c/pointerevents#45.
-
Value of button in a chorded pointerdown event w3c/pointerevents#4.
-
How removing target in pointer event handler affects compat mouse event target w3c/pointerevents#64.
-
Incorrect definition for primary pen (and possibly touch) w3c/pointerevents#54.
-
Pointer Id across different iframes w3c/pointerevents#52.
-
-
16 issues received 80 new comments.
-
Default width/height attribute for mouse w3c/pointerevents#65 (27 comments by @dmethvin, @mustaqahmed, @NavidZ, @patrickhlauke, @RByers, @scottgonzalez, @teddink)
-
Should a captured pointer send boundary events by default? w3c/pointerevents#566 (15 comments by @dmethvin, @NavidZ, @patrickhlauke, @RByers, @scottgonzalez, @smaug----, @teddink)
-
Add additional digitizer/pen attributes: twist (rotation) w3c/pointerevents#25 (11 comments by @dfleck, @patrickhlauke, @RByers, @skibulk, @smaug----)
-
Only people with push access can have issues assigned to them w3c/pointerevents#55 (6 comments by @patrickhlauke, @RByers, @shepazu)
-
Touch-action isn't flexible enough for direction-specific behavior w3c/pointerevents#6 (5 comments by @dtapuska, @patrickhlauke, @RByers)
-
ReSpec error: "A custom SotD paragraph is required for your type of document." w3c/pointerevents#71 (2 comments by @patrickhlauke, @RByers)
-
Compatibility mouse transition events should reflect a single logical mouse pointer w3c/pointerevents#35 (2 comments by @RByers)
-
Configure this repo to use gitbot and the #pointerevents channel w3c/pointerevents#11 (2 comments by @patrickhlauke, @RByers)
-
When are lost/gotpointercapture delayed until the next pointer event? w3c/pointerevents#32 (2 comments by @RByers, @teddink)
-
How removing target in pointer event handler affects compat mouse event target w3c/pointerevents#64 (2 comments by @NavidZ, @scottgonzalez)
-
Add additional digitizer/pen attributes: barrel pressure (tangential pressure) w3c/pointerevents#70 (1 comment by @patrickhlauke)
-
Incorrect definition for primary pen (and possibly touch) w3c/pointerevents#54 (1 comment by @patrickhlauke)
-
Incorrect order of the events in process pending pointer capture section w3c/pointerevents#39 (1 comment by @RByers)
-
-
5 pull requests opened.
-
Make width/height default to 1, remove UA "guessing"/faking geometry w3c/pointerevents#69, by @patrickhlauke.
-
Add new editor w3c/pointerevents#68, by @patrickhlauke.
-
Remove explicit "Status of this Document" w3c/pointerevents#67, by @patrickhlauke.
-
Make it explicit that buttons is a bitmask. w3c/pointerevents#66, by @mustaqahmed.
-
Clarified definition of capturing element borders w3c/pointerevents#63, by @NavidZ.
-
-
6 pull requests merged.
-
Made mouseover/out/enter/leave event firing independent of corresponding PEs w3c/pointerevents#56.
-
Make width/height default to 1, remove UA "guessing"/faking geometry w3c/pointerevents#69.
-
Add new editor w3c/pointerevents#68.
-
Remove explicit "Status of this Document" w3c/pointerevents#67.
-
Make it explicit that buttons is a bitmask. w3c/pointerevents#66.
-
Adding the scope of unique pointerId w3c/pointerevents#57.
-
-
8 pull requests received 41 new comments.
-
Made mouseover/out/enter/leave event firing independent of corresponding PEs w3c/pointerevents#56 (17 comments by @mustaqahmed, @patrickhlauke, @RByers)
-
Clarified definition of capturing element borders w3c/pointerevents#63 (11 comments by @mustaqahmed, @NavidZ, @RByers, @scottgonzalez)
-
Make width/height default to 1, remove UA "guessing"/faking geometry w3c/pointerevents#69 (5 comments by @mustaqahmed, @patrickhlauke, @RByers, @teddink)
-
Make it explicit that buttons is a bitmask. w3c/pointerevents#66 (4 comments by @patrickhlauke, @RByers, @scottgonzalez, @teddink)
-
Participants
-
2 organizations joined.
-
Mozilla Foundation joined.
-
OpenJS Foundation joined.
-
GitHub
w3c/pointerevents
-
8 issues opened.
-
Change the reference label for UI Events Specification w3c/pointerevents#60, by @mustaqahmed.
-
Should pointer IDs be unique even across different top-level browsing contexts? w3c/pointerevents#59, by @RByers.
-
Convert spec IDL to "contiguous" style w3c/pointerevents#58, by @RByers.
-
Only people with push access can have issues assigned to them w3c/pointerevents#55, by @RByers.
-
Incorrect definition for primary pen (and possibly touch) w3c/pointerevents#54, by @patrickhlauke.
-
Pointer Id across different iframes w3c/pointerevents#52, by @NavidZ.
-
MouseEvent.fromElement/toElement w3c/pointerevents#605, by @cvrebert.
-
PREVENT MOUSE EVENT flag is not well defined when multiple pointer types are active w3c/pointerevents#51, by @NavidZ.
-
-
3 issues closed.
-
Determining the primary pointer - note about mice? w3c/pointerevents#49.
-
What happens when an isPrimary pointer is removed? w3c/pointerevents#48.
-
PREVENT MOUSE EVENT flag is not well defined when multiple pointer types are active w3c/pointerevents#51.
-
-
7 issues received 23 new comments.
-
Pointer Id across different iframes w3c/pointerevents#52 (9 comments by @NavidZ, @patrickhlauke, @RByers)
-
Only people with push access can have issues assigned to them w3c/pointerevents#55 (4 comments by @patrickhlauke, @RByers, @shepazu)
-
Compatibility mouse transition events should reflect a single logical mouse pointer w3c/pointerevents#35 (3 comments by @jacobrossi, @RByers)
-
setPointerCapture should be disabled in sandboxed iframes by default w3c/pointerevents#16 (3 comments by @NavidZ, @RByers)
-
Determining the primary pointer - note about mice? w3c/pointerevents#49 (2 comments by @patrickhlauke, @RByers)
-
When are lost/gotpointercapture delayed until the next pointer event? w3c/pointerevents#32 (1 comment by @RByers)
-
PREVENT MOUSE EVENT flag is not well defined when multiple pointer types are active w3c/pointerevents#51 (1 comment by @patrickhlauke)
-
-
3 pull requests opened.
-
Adding the scope of unique pointerId w3c/pointerevents#57, by @NavidZ.
-
Made mouseover/out/enter/leave event firing independent of corresponding PEs w3c/pointerevents#56, by @mustaqahmed.
-
Rewrite of primary pointer section w3c/pointerevents#53, by @patrickhlauke.
-
-
2 pull requests merged.
-
Rewrite of primary pointer section w3c/pointerevents#53.
-
Cover the case when primary pointer is removed w3c/pointerevents#50.
-
-
4 pull requests received 38 new comments.
-
Made mouseover/out/enter/leave event firing independent of corresponding PEs w3c/pointerevents#56 (18 comments by @mustaqahmed, @RByers)
-
Rewrite of primary pointer section w3c/pointerevents#53 (17 comments by @mustaqahmed, @patrickhlauke, @RByers)
-
Cover the case when primary pointer is removed w3c/pointerevents#50 (2 comments by @mustaqahmed, @RByers)
-
Lifecycle
-
1 charter started.
-
Chartered until 31 January 2018. Participants had to rejoin under this charter.
-
Participants
-
2 participants left.
-
Michael[tm] Smith (sideshowbarker) (W3C) left.
-
Doug Schepers (W3C) left.
-
-
2 organizations joined.
-
TPGi joined.
-
Samsung Electronics Co., Ltd. joined.
-
-
10 organizations left.
-
Samsung Electronics Co., Ltd. left.
-
TPGi left.
-
Yandex left.
-
China Academy of Information and Communications Technology (CAICT) left.
-
Google LLC left.
-
OpenJS Foundation left.
-
Mozilla Foundation left.
-
Opera Software AS left.
-
Nokia Corporation left.
-
Microsoft Corporation left.
-
GitHub
w3c/pointerevents
-
9 issues opened.
-
Explain that mousedown focuses form controls w3c/pointerevents#604, by @cvrebert.
-
Determining the primary pointer - note about mice? w3c/pointerevents#49, by @patrickhlauke.
-
What happens when an isPrimary pointer is removed? w3c/pointerevents#48, by @patrickhlauke.
-
Respec's "Latest published version" w3c/pointerevents#46, by @patrickhlauke.
-
Should the spec really reference tracker anymore? w3c/pointerevents#45, by @RByers.
-
clarify what happens if touch-action is changed dynamically w3c/pointerevents#42, by @patrickhlauke.
-
touch-action - incorrect values in note for pull-to-refresh? w3c/pointerevents#41, by @patrickhlauke.
-
Incorrect order of the events in process pending pointer capture section w3c/pointerevents#39, by @NavidZ.
-
Consider adding API to get predicted points w3c/pointerevents#38, by @RByers.
-
-
4 issues closed.
-
touch-action - incorrect values in note for pull-to-refresh? w3c/pointerevents#41.
-
clarify what happens if touch-action is changed dynamically w3c/pointerevents#42.
-
Spec implies mice can't support pressure w3c/pointerevents#30.
-
Value of button attribute for pointermove event w3c/pointerevents#33.
-
-
1 issue reopened.
-
Proposal for UIEvent "role" property w3c/pointerevents#600, by @garykac.
-
-
17 issues received 53 new comments.
-
Respec's "Latest published version" w3c/pointerevents#46 (6 comments by @patrickhlauke, @RByers, @shepazu)
-
Compatibility mouse transition events should reflect a single logical mouse pointer w3c/pointerevents#35 (6 comments by @mustaqahmed, @NavidZ, @patrickhlauke, @teddink)
-
touch-action - incorrect values in note for pull-to-refresh? w3c/pointerevents#41 (5 comments by @patrickhlauke, @RByers)
-
Incorrect order of the events in process pending pointer capture section w3c/pointerevents#39 (5 comments by @mustaqahmed, @NavidZ, @RByers)
-
Add additional digitizer/pen attributes: twist (rotation) w3c/pointerevents#25 (4 comments by @dfleck, @patrickhlauke, @RByers)
-
Spec implies mice can't support pressure w3c/pointerevents#30 (4 comments by @patrickhlauke, @RByers, @scottgonzalez)
-
Should the spec really reference tracker anymore? w3c/pointerevents#45 (3 comments by @patrickhlauke, @RByers)
-
Value of button attribute for pointermove event w3c/pointerevents#33 (3 comments by @bethge, @patrickhlauke)
-
clarify what happens if touch-action is changed dynamically w3c/pointerevents#42 (2 comments by @patrickhlauke, @RByers)
-
Configure this repo to use gitbot and the #pointerevents channel w3c/pointerevents#11 (2 comments by @cynthia, @patrickhlauke)
-
-
6 pull requests opened.
-
Cover the case when primary pointer is removed w3c/pointerevents#50, by @NavidZ.
-
Switch to the W3C Software and Document license w3c/pointerevents#47, by @RByers.
-
Modify/clarify the example for directional touch-action values w3c/pointerevents#44, by @patrickhlauke.
-
clarification about dynamic touch-action changes w3c/pointerevents#43, by @patrickhlauke.
-
Reorder the events in process pending pointer capture w3c/pointerevents#40, by @NavidZ.
-
Future-proof by removing any mention of mouse/trackpad w3c/pointerevents#37, by @patrickhlauke.
-
-
5 pull requests merged.
-
Switch to the W3C Software and Document license w3c/pointerevents#47.
-
Modify/clarify the example for directional touch-action values w3c/pointerevents#44.
-
clarification about dynamic touch-action changes w3c/pointerevents#43.
-
Future-proof by removing any mention of mouse/trackpad w3c/pointerevents#37.
-
Add the missing pointerover/enter events w3c/pointerevents#36.
-
-
5 pull requests received 12 new comments.
-
Cover the case when primary pointer is removed w3c/pointerevents#50 (3 comments by @mustaqahmed, @patrickhlauke, @scottgonzalez)
-
Switch to the W3C Software and Document license w3c/pointerevents#47 (3 comments by @patrickhlauke, @RByers)
-
Modify/clarify the example for directional touch-action values w3c/pointerevents#44 (3 comments by @patrickhlauke, @RByers)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
Compatibility mouse transition events should reflect a single logical mouse pointer w3c/pointerevents#35, by @NavidZ.
-
-
4 issues received 14 new comments.
-
Value of button attribute for pointermove event w3c/pointerevents#33 (11 comments by @bethge, @patrickhlauke, @RByers, @smaug----, @teddink)
-
Compatibility mouse transition events should reflect a single logical mouse pointer w3c/pointerevents#35 (1 comment by @RByers)
-
-
2 pull requests opened.
-
Add the missing pointerover/enter events w3c/pointerevents#36, by @NavidZ.
-
Clarify the button value for mouse drag w3c/pointerevents#34, by @mustaqahmed.
-
-
1 pull request merged.
-
Clarify the button value for mouse drag w3c/pointerevents#34.
-
-
2 pull requests received 20 new comments.
-
Clarify the button value for mouse drag w3c/pointerevents#34 (15 comments by @mustaqahmed, @patrickhlauke, @RByers)
-
Add the missing pointerover/enter events w3c/pointerevents#36 (5 comments by @mustaqahmed, @NavidZ, @RByers, @teddink)
-
Participants
-
1 participant left.
-
Arthur Barstow (W3C Invited Experts) left.
-
GitHub
w3c/pointerevents
-
4 issues opened.
-
Value of button attribute for pointermove event w3c/pointerevents#33, by @bethge.
-
When are lost/gotpointercapture delayed until the next pointer event? w3c/pointerevents#32, by @NavidZ.
-
Spec implies mice can't support pressure w3c/pointerevents#30, by @RByers.
-
Add explicit control over pinch-zoom to touch-action w3c/pointerevents#565, by @RByers.
-
-
2 issues closed.
-
Explicit mention that `pan-x pan-y` is equivalent to `auto`? w3c/pointerevents#23.
-
equivalent of rotationAngle from Touch Events? w3c/pointerevents#28.
-
-
1 issue reopened.
-
Spec implies mice can't support pressure w3c/pointerevents#30, by @RByers.
-
-
6 issues received 21 new comments.
-
Expose 'direction-inversion' in wheel events w3c/pointerevents#586 (9 comments by @jacobrossi, @lorenbrichter, @RByers)
-
Spec implies mice can't support pressure w3c/pointerevents#30 (6 comments by @patrickhlauke, @RByers, @scottgonzalez)
-
Add explicit control over pinch-zoom to touch-action w3c/pointerevents#565 (3 comments by @patrickhlauke, @RByers)
-
When are lost/gotpointercapture delayed until the next pointer event? w3c/pointerevents#32 (1 comment by @RByers)
-
Explicit mention that `pan-x pan-y` is equivalent to `auto`? w3c/pointerevents#23 (1 comment by @patrickhlauke)
-
-
1 pull request opened.
-
Reword to not exclude ALL mice, include trackpads w3c/pointerevents#31, by @patrickhlauke.
-
-
1 pull request merged.
-
Reword to not exclude ALL mice, include trackpads w3c/pointerevents#31.
-