Slop suppression should only affect Touch Events |
||||||
Issue descriptionWe should send the pointer events immediately that occur inside the slop region. The slop region should only suppress the touch events. This is what Microsoft indicates they do. tdresser@ I don't think we have enough information currently in WebInputEvent to send the pointer events but not the touch events.
,
Jul 27 2016
Might be easiest to send the touch events to the renderer, but then filter them out before we dispatch them. That's a bit annoying for pages that don't have pointer events. We could keep two slop suppression implementations, and keep doing slop suppression in the touch event queue if there are no pointer event listeners. Maybe there could be some code sharing there?
,
Jul 27 2016
I think getting rid of touch slop suppression makes more sense. Even if we don't drop it entirely, moving the slop code into blink should be done before this. Therefore, blocking on crbug.com/593061 .
,
Jul 28 2016
SGTM.
,
Aug 24 2016
,
Sep 30 2016
,
Feb 8 2017
As expected, Lan's fix for Issue 593061 has fixed this problem. Just verified on Win Canary (58.0.3006.0) through http://rbyers.github.io/paint.html (which now uses PointerEvents), the slop is almost gone. There is still a bit of slop suppression there which I believe is done at device driver.
,
Feb 8 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dtapu...@chromium.org
, Jul 27 2016