New issue
Advanced search Search tips

Issue 692702 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Regression

Blocked on:
issue 682144

Blocking:
issue 691768



Sign in to add a comment

A cancelled touch-start should disable touch slop suppression

Project Member Reported by mustaq@chromium.org, Feb 15 2017

Issue description

We recently moved this into TouchEventManager but needed to move the check for cancelled touch-start as well.
 

Comment 1 by rbyers@chromium.org, Feb 16 2017

Labels: -Type-Bug M-58 Type-Bug-Regression
Which CL regressed this again?  It wasn't in M57, right?

Comment 2 by mustaq@chromium.org, Feb 16 2017

The CL causing this regression in M58 is crrev.com/2669663002.

We merged the CL to M57 beta then switched back. So M57 is unaffected.


Comment 3 by rbyers@chromium.org, Feb 16 2017

Labels: -Pri-2 Pri-1
Great, glad to hear M57 isn't affected - thanks!  Marking this Pri-1 for M58 to indicate we really don't want to ship this regression (it's subtle but pretty bad for drawing apps).

Comment 4 by mustaq@chromium.org, Feb 17 2017

Blocking: 691768

Comment 6 by mustaq@chromium.org, Feb 21 2017

Status: Fixed (was: Assigned)

Comment 7 by rbyers@chromium.org, Feb 22 2017

Blockedon: 682144
How does it affect mouse events PointerEvents?
Do we need to call e.preventDefault() on touchstart event to prevent slop suppression even when using a digitizer pen or a mouse?

In Chrome 56 slop suppression is affecting pen and mouse in paint apps.
There is no slop suppression for non-touch events. Perhaps you should open a new bug and provide details there.
Any PointerEvent based app that used to be affected by slop suppression will be fixed on M58, see  Issue 593061 . Please comment on that bug if your problems are not fixed in M58.

Sign in to add a comment