Tim, which version/channel are you running?

Passing along to Albert for triage.

I've seen it a few places now, ToT, and a fresh Chrome OS image

8339.0.0

Dev has the issue.

I can repro on 52.0.2733.0 on lulu

jdufault@ I know you're swamped with issues for 54, but I've got no one else to look at this. Can you take a quick peek?

 Issue 611499  has been merged into this issue.

See bug 158091. This was intentionally removed.

The timeout seems very long without any visual indication that something is happening. Was there any discussion of shortening it?

Owner to kuscher@ who requested/prioritized the removal (see linked bug 158091).

Is this really a stable blocker for R51 at this point?

Animation indeed removed intentionally.
If we want to shorten timing, we should look at other platforms to see what the timeout there is

Not a blocker

From rough tests with a timer, it seems to be ~700ms on Android vs ~1400ms on Chrome OS.

@jdufault, could we try out 700ms and see how that feels?

I dug around the android source, it looks like 500ms[1] is the standard, but it can be overridden.

1: http://androidxref.com/6.0.1_r10/xref/frameworks/base/core/java/android/view/ViewConfiguration.java#64

Moving this nonessential bug to the next milestone.

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

 Issue 603642  has been merged into this issue.

It would be really good to get this in for 53 because of Android apps.

jdufault@ I know your plate is full. Are you going to have time to land this or should I try to find someone else?

You can reassign to me if there is no one else and I'll prioritize this. The change should be very simple, just have to find what to change.

warx@ can you take this one as a high priority? 

OK. I will take a look into it.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ecd768b8eaa996dc371c67ffb9c3221808949712

commit ecd768b8eaa996dc371c67ffb9c3221808949712
Author: warx <warx@chromium.org>
Date: Thu Jun 16 16:22:50 2016

Changing long press timeout 1000ms to 500ms

The long press affordance is removed. Meanwhile, the long press time is still 1000ms which is too long. Change it to 500ms to align with standard.

BUG= 612890 

Review-Url: https://codereview.chromium.org/2064423003
Cr-Commit-Position: refs/heads/master@{#400167}

[modify] https://crrev.com/ecd768b8eaa996dc371c67ffb9c3221808949712/ui/events/gesture_detection/gesture_configuration.cc

changing long press time out config from 1000ms to 500ms.