Pointer Events Working Group - Activity in 2019
No matches.
TR publications
-
1 document published.
-
Pointer Events Level 3 published as a First Public Working Draft. History of Pointer Events Level 3
-
GitHub
w3c/pointerevents
-
1 issue closed.
-
CfC: Publication of PE3 as FPWD (ends 5 Dec 2019) w3c/pointerevents#312.
-
-
2 issues received 4 new comments.
-
touch-action doesn't allow for press-hold-drag UX w3c/pointerevents#178 (2 comments by @dmitryshimkin, @mustaqahmed)
-
CfC: Publication of PE3 as FPWD (ends 5 Dec 2019) w3c/pointerevents#312 (2 comments by @patrickhlauke)
-
-
1 pull request opened.
-
editorial: Avoid duplicate example_6 w3c/pointerevents#314, by @plehegar.
-
-
1 pull request merged.
-
editorial: Avoid duplicate example_6 w3c/pointerevents#314.
-
GitHub
w3c/pointerevents
-
3 issues opened.
-
CfC: Publication of PE3 as FPWD (ends 5 Dec 2019) w3c/pointerevents#312, by @patrickhlauke.
-
ReSpec error caused by MouseEventInit w3c/pointerevents#311, by @patrickhlauke.
-
Change DOM_DELTA_PIXEL to be intended scroll distance instead of exact scroll distance w3c/pointerevents#593, by @instylevii.
-
-
3 issues closed.
-
ReSpec error caused by MouseEventInit w3c/pointerevents#311.
-
Security & privacy considerations w3c/pointerevents#286.
-
-
3 issues received 10 new comments.
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (8 comments by @CWies, @masayuki-nakano)
-
-
3 pull requests opened.
-
Prevent the [[CSSOM-VIEW]] reference from pulling its internal references w3c/pointerevents#313, by @plehegar.
-
Remove extension doc w3c/pointerevents#310, by @NavidZ.
-
Add revision history up until now w3c/pointerevents#309, by @NavidZ.
-
-
5 pull requests merged.
-
Prevent the [[CSSOM-VIEW]] reference from pulling its internal references w3c/pointerevents#313.
-
Remove extension doc w3c/pointerevents#310.
-
Add revision history up until now w3c/pointerevents#309.
-
Add getPredictedEvents API w3c/pointerevents#307.
-
Define active document for the active pointers w3c/pointerevents#300.
-
-
3 pull requests received 5 new comments.
-
Prevent the [[CSSOM-VIEW]] reference from pulling its internal references w3c/pointerevents#313 (1 comment by @patrickhlauke)
GitHub
w3c/pointerevents
-
1 issue opened.
-
Need clarification how mouseenter/leave should behave while modifying DOM tree during event dispatch w3c/pointerevents#613, by @smaug----.
-
-
2 issues received 3 new comments.
-
Consider a simple API for low-latency pointer trails w3c/pointerevents#204 (2 comments by @dlibby-, @NavidZ)
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (1 comment by @masayuki-nakano)
-
-
4 pull requests opened.
-
Some slight rewording, for clarity w3c/pointerevents#308, by @patrickhlauke.
-
Add getPredictedEvents API w3c/pointerevents#307, by @NavidZ.
-
Introduce getCoalescedEvents API and pointerrawupdate event w3c/pointerevents#306, by @NavidZ.
-
fixing typo in Example 3 w3c/pointerevents#305, by @gked.
-
-
3 pull requests merged.
-
Some slight rewording, for clarity w3c/pointerevents#308.
-
Introduce getCoalescedEvents API and pointerrawupdate event w3c/pointerevents#306.
-
fixing typo in Example 3 w3c/pointerevents#305.
-
-
3 pull requests received 19 new comments.
-
Add getPredictedEvents API w3c/pointerevents#307 (15 comments by @NavidZ, @patrickhlauke, @smaug----)
-
Introduce getCoalescedEvents API and pointerrawupdate event w3c/pointerevents#306 (3 comments by @NavidZ)
-
GitHub
w3c/pointerevents
-
1 issue closed.
-
Update to constructor operations w3c/pointerevents#301.
-
-
1 issue reopened.
-
touch-action and scrolling directional lock w3c/pointerevents#303, by @graouts.
-
-
3 issues received 12 new comments.
-
Consider a simple API for low-latency pointer trails w3c/pointerevents#204 (3 comments by @dlibby-, @gked)
-
Enable direct pen and touch to have different touch-action behavior w3c/pointerevents#203 (2 comments by @BoCupp-Microsoft)
-
1 pull request opened.
-
Editorial: fix some ReSpec issues w3c/pointerevents#304, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: fix some ReSpec issues w3c/pointerevents#304.
-
GitHub
w3c/pointerevents
-
5 issues opened.
-
touch-action and scrolling directional lock w3c/pointerevents#303, by @graouts.
-
Update to constructor operations w3c/pointerevents#301, by @Ms2ger.
-
Suggestion. pointer-events: disabled w3c/pointerevents#299, by @ExtAnimal.
-
Update spec to new IDL syntax for optional dictionaries w3c/pointerevents#296, by @Ms2ger.
-
Set touch-action to allow web pages opt out Android back gesture w3c/pointerevents#295, by @LanWei22.
-
-
2 issues closed.
-
Suggestion. pointer-events: disabled w3c/pointerevents#299.
-
Too many other behaviors interrupt pointer events (dragstart, touch-action) w3c/pointerevents#213.
-
-
6 issues received 14 new comments.
-
Set touch-action to allow web pages opt out Android back gesture w3c/pointerevents#295 (6 comments by @graouts, @LanWei22, @NavidZ, @patrickhlauke)
-
Setting pointer capture on an element in a parent frame when the pointer was made active in a child frame w3c/pointerevents#291 (2 comments by @graouts, @NavidZ)
-
tiltX and tiltY aren't as helpful as just having altitude angle w3c/pointerevents#274 (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 @NavidZ)
-
-
6 pull requests opened.
-
Move Rick Byers to former editors w3c/pointerevents#302, by @patrickhlauke.
-
Define active document for the active pointers w3c/pointerevents#300, by @NavidZ.
-
Add dictionary default value w3c/pointerevents#298, by @saschanaz.
-
Set correct references for PE V3 w3c/pointerevents#297, by @NavidZ.
-
Add single-directional touch action values w3c/pointerevents#294, by @NavidZ.
-
Amend the note in pointercancel prevention w3c/pointerevents#293, by @NavidZ.
-
-
5 pull requests merged.
-
Move Rick Byers to former editors w3c/pointerevents#302.
-
Add single-directional touch action values w3c/pointerevents#294.
-
Set correct references for PE V3 w3c/pointerevents#297.
-
Add dictionary default value w3c/pointerevents#298.
-
Amend the note in pointercancel prevention w3c/pointerevents#293.
-
-
4 pull requests received 24 new comments.
-
Define active document for the active pointers w3c/pointerevents#300 (8 comments by @graouts, @NavidZ, @smaug----)
-
Add single-directional touch action values w3c/pointerevents#294 (8 comments by @graouts, @NavidZ, @patrickhlauke)
-
Add dictionary default value w3c/pointerevents#298 (6 comments by @NavidZ, @patrickhlauke, @saschanaz)
-
GitHub
w3c/pointerevents
-
1 issue opened.
-
Expand note about `click` / `contextmenu` w3c/pointerevents#292, by @patrickhlauke.
-
-
3 issues closed.
-
Extend pointer events to support raw trackpad data w3c/pointerevents#206.
-
touch-action: scroll || scroll-x || scroll-y w3c/pointerevents#211.
-
Pen Button Events w3c/pointerevents#290.
-
-
6 issues received 15 new comments.
-
Setting pointer capture on an element in a parent frame when the pointer was made active in a child frame w3c/pointerevents#291 (10 comments by @EiraGe, @NavidZ, @smaug----)
-
Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) w3c/pointerevents#592 (1 comment by @wisniewskit)
-
Extend pointer events to support raw trackpad data w3c/pointerevents#206 (1 comment by @patrickhlauke)
-
Enable direct pen and touch to have different touch-action behavior w3c/pointerevents#203 (1 comment by @patrickhlauke)
-
GitHub
w3c/pointerevents
-
5 issues opened.
-
Pen Button Events w3c/pointerevents#290, by @gked.
-
Update the WebKit status in README.md w3c/pointerevents#288, by @graouts.
-
Security & privacy considerations w3c/pointerevents#286, by @lknik.
-
1 issue closed.
-
Update the WebKit status in README.md w3c/pointerevents#288.
-
-
5 issues received 20 new comments.
-
Update the WebKit status in README.md w3c/pointerevents#288 (9 comments by @dtapuska, @graouts, @NavidZ, @patrickhlauke)
-
Should "click", "dblclick" and "contextmenu" events be PointerEvents? w3c/pointerevents#100 (2 comments by @BoCupp-Microsoft, @patrickhlauke)
-
Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers w3c/pointerevents#285 (1 comment by @NavidZ)
-
-
2 pull requests opened.
-
Update webkit status in README file w3c/pointerevents#289, by @NavidZ.
-
Add an explainer for the extension document w3c/pointerevents#287, by @NavidZ.
-
-
3 pull requests merged.
-
Update webkit status in README file w3c/pointerevents#289.
-
Add an explainer for the extension document w3c/pointerevents#287.
-
Clarify coalesce events and predicted event's target w3c/pointerevents#280.
-
-
4 pull requests received 37 new comments.
-
Add an explainer for the extension document w3c/pointerevents#287 (28 comments by @NavidZ, @patrickhlauke)
-
Clarify coalesce events and predicted event's target w3c/pointerevents#280 (5 comments by @annevk, @NavidZ)
-
Move single directional touch-action values to the extension spec w3c/pointerevents#238 (2 comments by @lpd-au, @NavidZ)
-
GitHub
w3c/pointerevents
-
4 issues opened.
-
Should pointer events and compatibility mouse events have the same timestamp? w3c/pointerevents#284, by @graouts.
-
pointerenter vs. pointerleave dispatch sequence w3c/pointerevents#283, by @graouts.
-
Click targeting is inconsistent across different UAs and the spec w3c/pointerevents#580, by @NavidZ.
-
It is unclear how predicted events' timestamps should relate to actual dispatched events w3c/pointerevents#282, by @smaug----.
-
-
3 issues closed.
-
pointerenter vs. pointerleave dispatch sequence w3c/pointerevents#283.
-
Should pointer events and compatibility mouse events have the same timestamp? w3c/pointerevents#284.
-
-
8 issues received 22 new comments.
-
pointerenter vs. pointerleave dispatch sequence w3c/pointerevents#283 (7 comments by @graouts, @NavidZ, @patrickhlauke)
-
Should pointer events and compatibility mouse events have the same timestamp? w3c/pointerevents#284 (5 comments by @graouts, @NavidZ, @RByers)
-
Click targeting is inconsistent across different UAs and the spec w3c/pointerevents#580 (3 comments by @NavidZ, @rniwa, @smaug----)
-
tiltX and tiltY aren't as helpful as just having altitude angle w3c/pointerevents#274 (2 comments by @dfleck, @k3a)
-
Dispatch of pointerover+pointerenter and pointerout+pointerleave in relation to related mouse events is not clearly specified w3c/pointerevents#279 (2 comments by @NavidZ, @patrickhlauke)
-
Click event is not fired when the node is removed and then added back w3c/pointerevents#576 (1 comment by @konard)
-
-
1 pull request opened.
-
Add better intro to the extension doc w3c/pointerevents#281, by @NavidZ.
-
-
1 pull request merged.
-
Add better intro to the extension doc w3c/pointerevents#281.
-
-
2 pull requests received 26 new comments.
-
Clarify coalesce events and predicted event's target w3c/pointerevents#280 (19 comments by @annevk, @EiraGe, @NavidZ)
-
TR publications
-
2 documents published.
-
Pointer Events published as a Recommendation. History of Pointer Events
-
Pointer Events published as a Recommendation. History of Pointer Events
-
GitHub
w3c/pointerevents
-
1 issue closed.
-
Define a low latency event that isn't occur in the document lifecycle w3c/pointerevents#214.
-
-
1 issue received 11 new comments.
-
MouseEvent.fromElement/toElement w3c/pointerevents#605 (11 comments by @foolip, @garykac, @hsivonen, @karlcow, @miketaylr)
-
-
1 pull request opened.
-
Clarify coalesce events and predicted event's target w3c/pointerevents#280, by @EiraGe.
-
-
1 pull request merged.
-
Introduce pointerrawupdate to address the high frequency usecases w3c/pointerevents#260.
-
-
2 pull requests received 6 new comments.
-
Introduce pointerrawupdate to address the high frequency usecases w3c/pointerevents#260 (4 comments by @NavidZ, @smaug----)
-
Clarify coalesce events and predicted event's target w3c/pointerevents#280 (2 comments by @annevk, @NavidZ)
-
GitHub
w3c/pointerevents
-
1 pull request received 5 new comments.
-
Introduce pointerrawupdate to address the high frequency usecases w3c/pointerevents#260 (5 comments by @NavidZ, @smaug----)
-
TR publications
-
1 document published.
-
Pointer Events published as a Proposed Recommendation. History of Pointer Events
-
GitHub
w3c/pointerevents
-
5 issues opened.
-
Immediately firing coalesced events for enter/leave/over/out? w3c/pointerevents#278, by @ChumpChief.
-
Limit pointerrawupdate and getCoalescedEvents API to secure origins w3c/pointerevents#277, by @NavidZ.
-
`touch-action: none` definition is too vague w3c/pointerevents#276, by @graouts.
-
mouseover/mouseout events can repeatedly causing infinite re-layout in some buggy content w3c/pointerevents#612, by @jidanni.
-
3 issues received 7 new comments.
-
Immediately firing coalesced events for enter/leave/over/out? w3c/pointerevents#278 (4 comments by @ChumpChief, @dtapuska)
-
Dispatch of pointerover+pointerenter and pointerout+pointerleave in relation to related mouse events is not clearly specified w3c/pointerevents#279 (2 comments by @graouts, @NavidZ)
-
Different mousedown behavior between Firefox and Chrome/Safari w3c/pointerevents#610 (1 comment by @nuragic)
-
-
1 pull request opened.
-
Use GlobalEventHandlers as a mixin w3c/pointerevents#275, by @foolip.
-
-
1 pull request merged.
-
Use GlobalEventHandlers as a mixin w3c/pointerevents#275.
-
-
1 pull request received 2 new comments.
GitHub
w3c/pointerevents
-
1 issue opened.
-
tiltX and tiltY aren't as helpful as just having altitude angle w3c/pointerevents#274, by @grorg.
-
-
4 issues received 20 new comments.
-
tiltX and tiltY aren't as helpful as just having altitude angle w3c/pointerevents#274 (15 comments by @dfleck, @grorg, @patrickhlauke)
-
MouseEvent.screenX/Y coordinate space is not clear w3c/pointerevents#607 (2 comments by @garykac, @mustaqahmed)
-
Add an API to get pre-coalesced points w3c/pointerevents#22 (2 comments by @patrickhlauke, @sigurdle)
-
-
1 pull request opened.
-
Fix ReSpec warnings w3c/pointerevents#273, by @saschanaz.
-
-
1 pull request merged.
-
Fix ReSpec warnings w3c/pointerevents#273.
-
-
2 pull requests received 12 new comments.
-
Introduce pointerrawupdate to address the high frequency usecases w3c/pointerevents#260 (7 comments by @NavidZ, @smaug----)
-