Wacom stylus shows slop suppression like behavior on Windows |
||
Issue descriptionNew issue created from crbug.com/593061#c31 comment: Tested with Chrome 58.0.3029.81 on a Tablet with Wacom digitizer running Windows 10. Slop superssion issue: 1. Go to http://rbyers.github.io/paint.html 2. Press the stylus on the screen. 3. Move the stylus very slowly and notice that you get the first PointerMove circle only after moving some distance. 4. Compare with Edge - you'll get the first PointerMove immediately. Touch blocks Stylus issue: 1. Go to http://rbyers.github.io/paint.html 2. Place your hand on the screen. 3. Try to draw with the stylus - you can't draw because your hand blocks stylus events.
,
Apr 21 2017
This is not related to touch-slop because in Windows, low-level stylus events are mouse events, not touch events. I was originally suspecting Wacom driver problem but that can't explain the Edge behavior. There is a chance WM_POINTER events are treated specially, e.g., not subjected to OS-level filtering. In that case, latest Chrome builds shouldn't show this problem. Lan, could you please verify this?
,
Apr 27 2017
Is there a Chrome version that uses WM_POINTER? Can I test it in Chrome Canary? Does using WM_POINTER also fix the problem with touch events blocking pen events?
,
May 5 2017
Simultaneous multitouch and pen input is tracked in https://bugs.chromium.org/p/chromium/issues/detail?id=701357
,
Aug 1 2017
Still need to check the pointer type in the slop suppression code once Windows sends touch events for this. |
||
►
Sign in to add a comment |
||
Comment 1 by mustaq@chromium.org
, Apr 21 2017