Don't send pointer events for touches that occur on an actively flinging element |
||||||
Issue descriptionSee https://github.com/w3c/pointerevents/issues/118 Once touch touches are passive and don't set/reset the touch-action ( issue 595327 ), then we should also be able to easily extend that to match Edge's behavior of not sending pointer events at all. We effectively remain in the "canceled" state until a touch occurs on something that is not currently flinging.
,
Mar 9 2017
What's the behavior here now that issue 595327 is fixed?
,
Mar 9 2017
Thanks for the heads up, I will take a look tomorrow.
,
Mar 10 2017
Tested on Android dev & ToT: PointerEvents on a flinging element didn't change from M56.
,
Mar 10 2017
Surprisingly, the cancelable bit of TouchEvents are not false during a fling. We tried both Android & CrOS.
,
Mar 10 2017
Repro for #5: jsbin.com/begolep, tried to fling on an ongoing fling. Should we reopen Issue 595327 ?
,
Mar 10 2017
,
Sep 7 2017
mustaq@ Is this something we shoudl fix in Q4?
,
Sep 7 2017
Sure. Marking it as "available" in case someone (eirage@?) can look into it before me.
,
Aug 1
,
Jan 18
(5 days ago)
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mustaq@chromium.org
, Jul 27 2016Status: Assigned (was: Available)