Pointer Events Working Group - Activity in 2017
No matches.
GitHub
w3c/pointerevents
-
5 issues received 16 new comments.
-
Click event while a pointer event is captured w3c/pointerevents#75 (9 comments by @freshp86, @NavidZ, @scottgonzalez)
-
The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec w3c/pointerevents#229 (2 comments by @mingchou, @NavidZ)
-
Mouse back/forward buttons: page navigation or JS events? w3c/pointerevents#191 (1 comment by @dtapuska)
-
GitHub
w3c/pointerevents
-
5 issues opened.
-
pointer-events for pseudo-elements w3c/pointerevents#230, by @laukstein.
-
The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec w3c/pointerevents#229, by @mingchou.
-
Expose wheel event scrolling state to DOM events w3c/pointerevents#591, by @sahel-sh.
-
Touch/Trackpad finger position w3c/pointerevents#228, by @felipenmoura.
-
Should getCoalescedEvents() return always the same objects or new instances with same data? w3c/pointerevents#227, by @smaug----.
-
-
1 issue closed.
-
pointer-events for pseudo-elements w3c/pointerevents#230.
-
-
12 issues received 52 new comments.
-
The behavior of getCoalescedEvent in pointerevent_constructor.html is inconsistent with the spec w3c/pointerevents#229 (9 comments by @NavidZ, @smaug----)
-
Expose wheel event scrolling state to DOM events w3c/pointerevents#591 (8 comments by @bokand, @dtapuska, @RByers, @sahel-sh, @staktrace)
-
"This API always returns at least one coalesced event for pointermove events and an empty list for other types of PointerEvents." w3c/pointerevents#224 (7 comments by @NavidZ, @smaug----)
-
Mouse back/forward buttons: page navigation or JS events? w3c/pointerevents#191 (5 comments by @dtapuska, @jstenback, @mustaqahmed, @smaug----)
-
What should be the width/height of touch pointerUp? w3c/pointerevents#225 (5 comments by @mingchou, @mustaqahmed, @NavidZ)
-
Should getCoalescedEvents() return always the same objects or new instances with same data? w3c/pointerevents#227 (4 comments by @NavidZ, @smaug----)
-
When to continue firing pointer events after a drag operation? w3c/pointerevents#222 (3 comments by @mingchou, @NavidZ)
-
GitHub
w3c/pointerevents
-
9 issues opened.
-
Can one active pointer cancel other pointers of different types? w3c/pointerevents#226, by @mustaqahmed.
-
What should be the width/height of touch pointerUp? w3c/pointerevents#225, by @EiraGe.
-
Activation behavior and click interaction is not specified w3c/pointerevents#578, by @bzbarsky.
-
How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit w3c/pointerevents#223, by @smaug----.
-
When to continue firing pointer events after a drag operation? w3c/pointerevents#222, by @mingchou.
-
Should setPointerCapture work in Shadow DOM w3c/pointerevents#221, by @smaug----.
-
It isn't clear what "page" means in "Setting Pointer Capture" w3c/pointerevents#220, by @smaug----.
-
-
10 issues received 18 new comments.
-
How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit w3c/pointerevents#223 (5 comments by @dtapuska, @NavidZ, @smaug----)
-
Add OS image dragging to non-normative reasons for pointercancel w3c/pointerevents#205 (4 comments by @appsforartists, @NavidZ, @patrickhlauke, @RByers)
-
What should be the width/height of touch pointerUp? w3c/pointerevents#225 (2 comments by @EiraGe, @mingchou)
-
Enable direct pen and touch to have different touch-action behavior w3c/pointerevents#203 (1 comment by @phistuck)
-
When to continue firing pointer events after a drag operation? w3c/pointerevents#222 (1 comment by @mingchou)
-
How should PointerLock vs setPointerCapture work together? w3c/pointerevents#176 (1 comment by @smaug----)
-
GitHub
w3c/pointerevents
-
3 issues opened.
-
Can any code be run between mouseup and click handlers? w3c/pointerevents#577, by @NavidZ.
-
Add [Exposed] to all interfaces w3c/pointerevents#217, by @annevk.
-
Imperative API to request suppression of panning and zooming w3c/pointerevents#216, by @RByers.
-
-
1 issue closed.
-
Add [Exposed] to all interfaces w3c/pointerevents#217.
-
-
3 issues received 16 new comments.
-
Imperative API to request suppression of panning and zooming w3c/pointerevents#216 (11 comments by @dtapuska, @flackr, @mdittmer, @mustaqahmed, @RByers)
-
-
1 pull request opened.
-
Add [Exposed=Window] to Constructor w3c/pointerevents#218, by @patrickhlauke.
-
-
1 pull request merged.
-
Add [Exposed=Window] to Constructor w3c/pointerevents#218.
-
GitHub
w3c/pointerevents
-
2 issues opened.
-
Difficulty understanding getCoalescedEvents definition w3c/pointerevents#215, by @gsnedders.
-
Define a low latency event that isn't occur in the document lifecycle w3c/pointerevents#214, by @dtapuska.
-
-
3 issues received 18 new comments.
-
Define a low latency event that isn't occur in the document lifecycle w3c/pointerevents#214 (13 comments by @dtapuska, @RByers, @Rycochet, @scottgonzalez, @smaug----)
-
Difficulty understanding getCoalescedEvents definition w3c/pointerevents#215 (4 comments by @dtapuska, @gsnedders, @NavidZ, @patrickhlauke)
-
GitHub
w3c/pointerevents
-
3 issues opened.
-
Too many other behaviors interrupt pointer events (dragstart, touch-action) w3c/pointerevents#213, by @appsforartists.
-
MouseEvent.screenX/Y coordinate space is not clear w3c/pointerevents#607, by @NavidZ.
-
Would pointerType === 'pen' events participate in HTML5 Drag & Drop? w3c/pointerevents#212, by @nicholaswmin.
-
-
3 issues closed.
-
tangentialPressure support in browsers w3c/pointerevents#192.
-
Should DnD release pointer capture? w3c/pointerevents#194.
-
Add OS image dragging to non-normative reasons for pointercancel w3c/pointerevents#205.
-
-
1 issue reopened.
-
Would pointerType === 'pen' events participate in HTML5 Drag & Drop? w3c/pointerevents#212, by @nicholaswmin.
-
-
5 issues received 18 new comments.
-
MouseEvent.screenX/Y coordinate space is not clear w3c/pointerevents#607 (11 comments by @bokand, @NavidZ, @RByers, @smaug----)
-
Would pointerType === 'pen' events participate in HTML5 Drag & Drop? w3c/pointerevents#212 (4 comments by @NavidZ, @nicholaswmin)
-
Add OS image dragging to non-normative reasons for pointercancel w3c/pointerevents#205 (1 comment by @NavidZ)
-
-
1 pull request merged.
-
Define the interation of drag operation vs capture w3c/pointerevents#201.
-
-
1 pull request received 5 new comments.
-
Define the interation of drag operation vs capture w3c/pointerevents#201 (5 comments by @appsforartists, @mustaqahmed, @NavidZ)
-
GitHub
w3c/pointerevents
-
1 issue closed.
-
Clarify what touch-action allows with rotated scrollable elements w3c/pointerevents#115.
-
-
5 issues received 25 new comments.
-
Add OS image dragging to non-normative reasons for pointercancel w3c/pointerevents#205 (14 comments by @appsforartists, @NavidZ, @patrickkettner, @RByers)
-
tangentialPressure support in browsers w3c/pointerevents#192 (6 comments by @mingchou, @NavidZ, @patrickhlauke)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (2 comments by @patrickkettner, @RByers)
-
Clarify what touch-action allows with rotated scrollable elements w3c/pointerevents#115 (1 comment by @mustaqahmed)
-
-
1 pull request received 3 new comments.
-
Define the interation of drag operation vs capture w3c/pointerevents#201 (3 comments by @mustaqahmed, @NavidZ)
-
GitHub
w3c/pointerevents
-
9 issues opened.
-
touch-action: scroll || scroll-x || scroll-y w3c/pointerevents#211, by @appsforartists.
-
offsetX/offsetY is confusing for GetCoalescedEvents w3c/pointerevents#209, by @RByers.
-
Should the spec defines how to handle when the pen's left button and the pen tip both are pressed? w3c/pointerevents#207, by @LanWei22.
-
Extend pointer events to support raw trackpad data w3c/pointerevents#206, by @RByers.
-
Add OS image dragging to non-normative reasons for pointercancel w3c/pointerevents#205, by @appsforartists.
-
Consider a simple API for low-latency pointer trails w3c/pointerevents#204, by @RByers.
-
Enable direct pen and touch to have different touch-action behavior w3c/pointerevents#203, by @RByers.
-
Normatively make touch-action apply for direct-manipulation pen devices w3c/pointerevents#202, by @RByers.
-
Click event is not fired when the node is removed and then added back w3c/pointerevents#576, by @NavidZ.
-
-
2 issues closed.
-
How should PointerLock vs setPointerCapture work together? w3c/pointerevents#176.
-
offsetX/offsetY is confusing for GetCoalescedEvents w3c/pointerevents#209.
-
-
1 issue reopened.
-
How should PointerLock vs setPointerCapture work together? w3c/pointerevents#176, by @NavidZ.
-
-
14 issues received 75 new comments.
-
Add OS image dragging to non-normative reasons for pointercancel w3c/pointerevents#205 (32 comments by @appsforartists, @mustaqahmed, @NavidZ, @NekR, @smaug----)
-
Enable direct pen and touch to have different touch-action behavior w3c/pointerevents#203 (14 comments by @mustaqahmed, @NekR, @patrickhlauke, @patrickkettner, @RByers, @scottgonzalez)
-
Click event is not fired when the node is removed and then added back w3c/pointerevents#576 (5 comments by @annevk, @domenic, @dtapuska, @NavidZ, @smaug----)
-
Normatively make touch-action apply for direct-manipulation pen devices w3c/pointerevents#202 (4 comments by @patrickhlauke, @RByers)
-
offsetX/offsetY is confusing for GetCoalescedEvents w3c/pointerevents#209 (3 comments by @NavidZ, @RByers, @wffurr)
-
How should PointerLock vs setPointerCapture work together? w3c/pointerevents#176 (2 comments by @NavidZ)
-
Should the spec defines how to handle when the pen's left button and the pen tip both are pressed? w3c/pointerevents#207 (2 comments by @dfleck, @scottgonzalez)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (1 comment by @mustaqahmed)
-
-
2 pull requests opened.
-
Set target for coalesced events w3c/pointerevents#210, by @NavidZ.
-
Fixed coordinate space for touch-action w3c/pointerevents#208, by @mustaqahmed.
-
-
3 pull requests merged.
-
Set target for coalesced events w3c/pointerevents#210.
-
Fixed coordinate space for touch-action w3c/pointerevents#208.
-
Clarify pointer capture behavior when pointer lock is applied w3c/pointerevents#196.
-
-
5 pull requests received 8 new comments.
-
Add notes about touch-action and direct/indirect manipulation and stylus w3c/pointerevents#188 (1 comment by @RByers)
-
Clarify pointer capture behavior when pointer lock is applied w3c/pointerevents#196 (1 comment by @NavidZ)
GitHub
w3c/pointerevents
-
3 issues opened.
-
Should events queue a task? w3c/pointerevents#571, by @jakearchibald.
-
Should DnD release pointer capture? w3c/pointerevents#194, by @NavidZ.
-
tangentialPressure support in browsers w3c/pointerevents#192, by @patrickhlauke.
-
-
2 issues closed.
-
Add an API to get pre-coalesced points w3c/pointerevents#22.
-
pointerType: 'dial' w3c/pointerevents#152.
-
-
2 issues reopened.
-
Specify MouseEvent.which w3c/pointerevents#601, by @garykac.
-
Clarify what touch-action allows with rotated scrollable elements w3c/pointerevents#115, by @mustaqahmed.
-
-
14 issues received 62 new comments.
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (14 comments by @lpd-au, @mustaqahmed, @patrickhlauke, @patrickkettner, @RByers, @saschanaz)
-
Clarify what touch-action allows with rotated scrollable elements w3c/pointerevents#115 (12 comments by @mustaqahmed, @patrickhlauke, @RByers)
-
tangentialPressure support in browsers w3c/pointerevents#192 (6 comments by @dfleck, @mustaqahmed, @NavidZ, @patrickhlauke)
-
Should events queue a task? w3c/pointerevents#571 (6 comments by @dtapuska, @jakearchibald, @patrickhlauke)
-
Mouse back/forward buttons: page navigation or JS events? w3c/pointerevents#191 (3 comments by @lpd-au, @mustaqahmed, @smaug----)
-
ReSpec warning on "Privacy and Security" w3c/pointerevents#183 (3 comments by @marcoscaceres, @patrickhlauke)
-
Click event while a pointer event is captured w3c/pointerevents#75 (2 comments by @patrickkettner, @scottgonzalez)
-
Some tests don't work properly with mobile-sized viewports w3c/pointerevents#139 (1 comment by @patrickhlauke)
-
Consider having explicit capture (sometimes) include boundary events w3c/pointerevents#143 (1 comment by @patrickhlauke)
-
-
7 pull requests opened.
-
Define the interation of drag operation vs capture w3c/pointerevents#201, by @NavidZ.
-
Clarified the touch-action values for transformed elements. w3c/pointerevents#200, by @mustaqahmed.
-
Revert "Clarified the touch-action values for transformed elements" w3c/pointerevents#199, by @patrickhlauke.
-
Clarified the touch-action values for transformed elements. w3c/pointerevents#198, by @mustaqahmed.
-
Clarify pointer capture behavior when pointer lock is applied w3c/pointerevents#196, by @LanWei22.
-
Update editors list w3c/pointerevents#195, by @patrickhlauke.
-
Add security/privacy considerations w3c/pointerevents#193, by @patrickhlauke.
-
-
4 pull requests merged.
-
Clarified the touch-action values for transformed elements. w3c/pointerevents#200.
-
Revert "Clarified the touch-action values for transformed elements" w3c/pointerevents#199.
-
Clarified the touch-action values for transformed elements. w3c/pointerevents#198.
-
Update editors list w3c/pointerevents#195.
-
-
4 pull requests received 31 new comments.
-
Clarified the touch-action values for transformed elements. w3c/pointerevents#198 (18 comments by @mustaqahmed, @patrickhlauke)
-
Add security/privacy considerations w3c/pointerevents#193 (7 comments by @annevk, @marcoscaceres, @patrickhlauke, @tomrittervg)
-
Clarify pointer capture behavior when pointer lock is applied w3c/pointerevents#196 (5 comments by @NavidZ, @patrickkettner)
-
Clarified the touch-action values for transformed elements. w3c/pointerevents#200 (1 comment by @patrickhlauke)
-
GitHub
w3c/pointerevents
-
6 issues opened.
-
Mouse back/forward buttons: page navigation or JS events? w3c/pointerevents#191, by @mustaqahmed.
-
Add WheelEvent#wheelDelta/wheelDeltaX/wheelDeltaY w3c/pointerevents#590, by @foolip.
-
Set coalesced events isTrusted flag to false w3c/pointerevents#187, by @NavidZ.
-
The spec is unclear whether boundary events should fire while pointer is captured to a certain target w3c/pointerevents#185, by @smaug----.
-
The spec doesn't define the values for relatedTarget w3c/pointerevents#184, by @smaug----.
-
ReSpec warning on "Privacy and Security" w3c/pointerevents#183, by @patrickhlauke.
-
-
6 issues closed.
-
Set coalesced events isTrusted flag to false w3c/pointerevents#187.
-
The spec doesn't define the values for relatedTarget w3c/pointerevents#184.
-
illustration for "twist" ? w3c/pointerevents#88.
-
Would be good to better clarify pointer event firing w3c/pointerevents#569.
-
1 issue reopened.
-
Click event while a pointer event is captured w3c/pointerevents#75, by @NavidZ.
-
-
9 issues received 35 new comments.
-
Set coalesced events isTrusted flag to false w3c/pointerevents#187 (10 comments by @dtapuska, @RByers, @smaug----)
-
Add WheelEvent#wheelDelta/wheelDeltaX/wheelDeltaY w3c/pointerevents#590 (8 comments by @foolip, @garykac, @masayuki-nakano)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (4 comments by @lpd-au, @NavidZ, @patrickkettner)
-
The spec doesn't define the values for relatedTarget w3c/pointerevents#184 (4 comments by @patrickhlauke, @smaug----)
-
What is the relationship between setPointerCapture, PointerLock, and browser default behaviors? w3c/pointerevents#135 (3 comments by @mingchou, @NavidZ)
-
Need a test for 'touch-action: pinch-zoom` and `touch-action: pan-x pan-y' behavior for multi-finger panning w3c/pointerevents#166 (2 comments by @mustaqahmed, @NavidZ)
-
Pointer events & disabled form elements w3c/pointerevents#177 (2 comments by @OliverJAsh, @smaug----)
-
-
6 pull requests opened.
-
Clarify the relatedTarget definition for pointerevents w3c/pointerevents#190, by @NavidZ.
-
Set isTrusted for coalesced events w3c/pointerevents#189, by @NavidZ.
-
Add notes about touch-action and direct/indirect manipulation and stylus w3c/pointerevents#188, by @patrickhlauke.
-
Clear the definition of boudnary events in capturing scenarios w3c/pointerevents#186, by @NavidZ.
-
Expand list of aknowledgements w3c/pointerevents#182, by @patrickhlauke.
-
Change respecConf URLs from http to https w3c/pointerevents#181, by @patrickhlauke.
-
-
9 pull requests merged.
-
Set isTrusted for coalesced events w3c/pointerevents#189.
-
Clarify the relatedTarget definition for pointerevents w3c/pointerevents#190.
-
Add notes about touch-action and direct/indirect manipulation and stylus w3c/pointerevents#188.
-
Clear the definition of boudnary events in capturing scenarios w3c/pointerevents#186.
-
Define coalesced events target, currentTarget, and eventPhase w3c/pointerevents#179.
-
Expand list of aknowledgements w3c/pointerevents#182.
-
Define the ordering of click event and lostpointercapture w3c/pointerevents#174.
-
Clarified event attributes. w3c/pointerevents#170.
-
Change respecConf URLs from http to https w3c/pointerevents#181.
-
-
8 pull requests received 23 new comments.
-
Set isTrusted for coalesced events w3c/pointerevents#189 (6 comments by @NavidZ, @RByers, @smaug----, @tabatkins)
-
Define the ordering of click event and lostpointercapture w3c/pointerevents#174 (5 comments by @NavidZ, @patrickhlauke)
-
Clarify the relatedTarget definition for pointerevents w3c/pointerevents#190 (2 comments by @mustaqahmed, @NavidZ)
-
Add notes about touch-action and direct/indirect manipulation and stylus w3c/pointerevents#188 (2 comments by @patrickhlauke)
-
Clear the definition of boudnary events in capturing scenarios w3c/pointerevents#186 (2 comments by @scottgonzalez, @smaug----)
-
Define coalesced events target, currentTarget, and eventPhase w3c/pointerevents#179 (2 comments by @dtapuska, @NavidZ)
-
GitHub
w3c/pointerevents
-
5 issues opened.
-
Specify the arguments of initMouseEvent() w3c/pointerevents#606, by @foolip.
-
Standardize layerX/layerY on MouseEvent w3c/pointerevents#626, by @dtapuska.
-
touch-action doesn't allow for press-hold-drag UX w3c/pointerevents#178, by @RByers.
-
Pointer events & disabled form elements w3c/pointerevents#177, by @jakearchibald.
-
How should PointerLock vs setPointerCapture work together? w3c/pointerevents#176, by @mustaqahmed.
-
-
1 issue closed.
-
Incorrect movementX/Y in PointerEvents w3c/pointerevents#567.
-
-
5 issues received 33 new comments.
-
Pointer events & disabled form elements w3c/pointerevents#177 (23 comments by @dmethvin, @domenic, @dtapuska, @garykac, @jakearchibald, @mustaqahmed, @RByers, @scottgonzalez, @smaug----, @tkent-google)
-
touch-action doesn't allow for press-hold-drag UX w3c/pointerevents#178 (4 comments by @RByers, @staktrace)
-
Standardize layerX/layerY on MouseEvent w3c/pointerevents#626 (3 comments by @dtapuska, @foolip, @smaug----)
-
How should PointerLock vs setPointerCapture work together? w3c/pointerevents#176 (2 comments by @mustaqahmed, @NavidZ)
-
What is the relationship between setPointerCapture, PointerLock, and browser default behaviors? w3c/pointerevents#135 (1 comment by @mustaqahmed)
-
-
4 pull requests opened.
-
Add pan/zoom in the non-normative examples for pointercancel w3c/pointerevents#180, by @patrickhlauke.
-
Define coalesced events target, currentTarget, and eventPhase w3c/pointerevents#179, by @NavidZ.
-
Fix a few typos in the extension doc w3c/pointerevents#175, by @NavidZ.
-
Define the ordering of click event and lostpointercapture w3c/pointerevents#174, by @NavidZ.
-
-
2 pull requests merged.
-
Add pan/zoom in the non-normative examples for pointercancel w3c/pointerevents#180.
-
Fix a few typos in the extension doc w3c/pointerevents#175.
-
-
1 pull request closed.
-
Add pinch-zoom token to touch-action w3c/pointerevents#99.
-
-
4 pull requests received 6 new comments.
-
Define coalesced events target, currentTarget, and eventPhase w3c/pointerevents#179 (2 comments by @dtapuska, @NavidZ)
-
Define the ordering of click event and lostpointercapture w3c/pointerevents#174 (1 comment by @RByers)
-
Participants
-
1 participant joined.
-
Philippe Le Hegaret (W3C) joined.
-
-
1 participant left.
-
Doug Schepers (W3C) left.
-
GitHub
w3c/pointerevents
-
6 issues opened.
-
Should pointer capture work when element is in non-browsing-context w3c/pointerevents#172, by @smaug----.
-
Behaviour of dblclicks is not specified w3c/pointerevents#171, by @IvanSanchez.
-
Element for dblclick when dblclick results of two clicks on different elements w3c/pointerevents#575, by @maxired.
-
Behavior of PointerEvent.fromElement/toElement w3c/pointerevents#167, by @RByers.
-
3 issues closed.
-
New respec warnings about missing dfns w3c/pointerevents#163.
-
Touch-action should distinguish between single- vs multi-finger panning w3c/pointerevents#159.
-
-
13 issues received 33 new comments.
-
Need a test for 'touch-action: pinch-zoom` and `touch-action: pan-x pan-y' behavior for multi-finger panning w3c/pointerevents#166 (5 comments by @mustaqahmed, @NavidZ, @RByers)
-
setPointerCapture should be disabled in sandboxed iframes by default w3c/pointerevents#16 (4 comments by @RByers, @scheib)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (4 comments by @NavidZ, @RByers, @smaug----)
-
Would be good to better clarify pointer event firing w3c/pointerevents#569 (3 comments by @mustaqahmed, @RByers)
-
Touch-action should distinguish between single- vs multi-finger panning w3c/pointerevents#159 (3 comments by @mustaqahmed, @RByers)
-
Should pointer capture work when element is in non-browsing-context w3c/pointerevents#172 (2 comments by @mustaqahmed, @smaug----)
-
What is the relationship between setPointerCapture, PointerLock, and browser default behaviors? w3c/pointerevents#135 (1 comment by @RByers)
-
Should spec mention OS/UA features like palm rejection? w3c/pointerevents#165 (1 comment by @RByers)
-
-
3 pull requests opened.
-
Clarified event attributes. w3c/pointerevents#170, by @mustaqahmed.
-
Add ReSpec "no-link-warnings" w3c/pointerevents#169, by @patrickhlauke.
-
Fix most ReSpec warnings w3c/pointerevents#168, by @patrickhlauke.
-
-
2 pull requests merged.
-
Add ReSpec "no-link-warnings" w3c/pointerevents#169.
-
Fix most ReSpec warnings w3c/pointerevents#168.
-