922d8d091b
Bug 1511231 - Part 4: s/ProcessPendingColaescedTouchData/ProcessPendingCoalescedTouchData/; r=smaug
...
Differential Revision: https://phabricator.services.mozilla.com/D122723
2021-08-19 13:27:13 +00:00
6a90d4510a
Bug 1511231 - Part 3: Expose coalesced Touches to PointerEvent.getCoalescedEvents(); r=smaug
...
Differential Revision: https://phabricator.services.mozilla.com/D122590
2021-08-19 13:27:12 +00:00
b8a9a605d8
Backed out 4 changesets (bug 1511231) for causing cpp bustages in CoalescedTouchData.cpp
...
CLOSED TREE
Backed out changeset 79dc991bfa6c (bug 1511231151123115112311511231
2021-08-19 13:19:11 +03:00
f8b397ad5f
Bug 1511231 - Part 4: s/ProcessPendingColaescedTouchData/ProcessPendingCoalescedTouchData/; r=smaug
...
Differential Revision: https://phabricator.services.mozilla.com/D122723
2021-08-19 09:08:20 +00:00
f0fd7b7998
Bug 1511231 - Part 3: Expose coalesced Touches to PointerEvent.getCoalescedEvents(); r=smaug
...
Differential Revision: https://phabricator.services.mozilla.com/D122590
2021-08-19 09:08:20 +00:00
9a4b0f2c7f
Bug 1725493 - Make coalesced touchmove event could be up-to-date; r=smaug,sefeng
...
`mChanged` isn't propagated through IPC, so we end up never update the coalesced
event. There can't be too many of touches, so it shouldn't be a performance
issue if we just update all touches.
Differential Revision: https://phabricator.services.mozilla.com/D122539
2021-08-18 16:02:49 +00:00
b366fba33e
Bug 1712825 - Allow coalescing touchmove events in BrowserChild r=smaug
...
Differential Revision: https://phabricator.services.mozilla.com/D116625
2021-06-07 15:29:15 +00:00
Edgar Chen
Alexandru Michis
Sean Feng