New issue
Advanced search Search tips

Issue 608116 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Flick gestures cause mousedown and mousemove events to be lost when using a stylus

Reported by jorgeagu...@gmail.com, Apr 30 2016

Issue description

Chrome Version       : 50.0.2661.94 m
URLs (if applicable) :
http://stackoverflow.com/questions/36877410/how-can-i-disable-flick-behavior-in-a-browser-chrome-firefox/36947911#36947911
https://github.com/jogonzal/MinimalisticFlickDelayRepro

Other browsers tested: IE, Edge, Firefox
         IE: PASS ()
    Firefox: FAIL ()
       Edge: PASS ()

(Entire repro/files contained in https://github.com/jogonzal/MinimalisticFlickDelayRepro)

Repro

1. Open index.html
2. On a Surface Pro 3 or 4, in Chrome or Firefox, try inking from left to right quickly with the stylus. You can also try inking in a curve to notice the missing dots.
For a video of this behavior, see the video attached (ReproChrome.mp4, ReproFireFox.mp4)

Expected

The inking is fluid.

Actual

The inking is not fluid - the mousedown event is delayed an a significant number of mousemove events are missing. Flick events show up when inking in the canvas because the browser app is subscribed to "flick" events described here: https://msdn.microsoft.com/en-us/library/ms703447%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

This does not repro in IE or Edge. In fact, those browsers have turned off support for flick gestures completely. Chrome and Firefox should do the same (Windows 10 apps no longer support flicks, so the OS seems to be moving away from this)

Please provide any additional information below. Attach a screenshot if
possible.

Screenshots, videos a repro website and a proposed fix included in the github repository.
https://github.com/jogonzal/MinimalisticFlickDelayRepro
 
Please feel free to contact me for any questions regarding this issue. I am a Microsoft employee working on a web application.

Comment 2 by ajha@chromium.org, May 3 2016

Cc: kylixrd@chromium.org ajha@chromium.org
Components: Internals>Input>Touch>Screen
Cc'ing  kylixrd@ for more inputs and further investigation of this.
A fix that should cover this issue was committed April 7: https://chromium.googlesource.com/chromium/src/+/fd3c1f989b2e3012be9e6cffdb6bfa86b9fda99e

It should be in the Canary builds by now. Please try again there.
Verified this is in fact fixed in the latest canary build (52.0.2723.0). I added this details on https://github.com/jogonzal/MinimalisticFlickDelayRepro
Project Member

Comment 5 by sheriffbot@chromium.org, May 4 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment