New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 599043 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
no longer active
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

DOM element that appears in tapped location becomes focused.

Reported by jshan...@etouch.net, Mar 30 2016

Issue description

Chrome Version: 51.0.2694.1 (Official Build) d916c77d6610e3821101f1c7baf099f4982a1662-refs/branch-heads/2694@{#1}-32/64 bit
OS: Windows 10 (Touch device)

Precondition: Enabled 'Media Router' flag from chrome://flags

Steps:
(1) Launch chrome,click on 'Cast' option from wrench menu or from context menu.
(2) Tap/touch on 'Cast to' option and observe.

Actual: Unnecessary highlight is seen on 'Cast desktop' option after tap/touch on 'Cast to' option.

Expected: No such highlight should be seen on 'Cast desktop' option after tap/touch on 'Cast to' option.

This is a regression issue broken in M-51, will soon update the bisect info.

Good build: 51.0.2690.0
Bad build: 51.0.2691.0

Note: This is touch specific issue, same works fine on mouse click.
 

 
Actual_result.mp4
875 KB Download
Expected_result.mp4
474 KB Download

Comment 1 by jshan...@etouch.net, Mar 30 2016

Components: Internals>Input>Touch>Screen
Labels: Proj-Windows10 hasbisect
Owner: apaci...@chromium.org
Status: Assigned (was: Unconfirmed)
Narrow bisect:
https://chromium.googlesource.com/chromium/src/+log/5b1e167ce1d26257ec579d9fdcadab8a70360f9c..99a9fd01df438f41d7192e6581fe7b1cb4f18d99?pretty=fuller&n=100

Suspecting: r383395 ?

Please help to re-assign if your change is not the cause.
Labels: -Pri-1 Pri-2
Labels: -Proj-Windows10 OS-Chrome OS-Linux OS-Mac
Summary: DOM element that appears under tapped location becomes focused. (was: Regression: Unnecessary highlight is seen on 'Cast desktop' option after tap/touch on 'Cast to'.)
This was introduced after switching clicks to taps.

Any DOM element that appears under the tapped location becomes focused. This happens whenever the view switches, and on all platforms.
Status: ExternalDependency (was: Assigned)
Summary: DOM element that appears in tapped location becomes focused. (was: DOM element that appears under tapped location becomes focused.)
I can repro this issue using a basic Polymer demo: https://github.com/japacible/tap-switch-menu

I've filed an issue:
https://github.com/Polymer/polymer/issues/3561

If we switch back to "click" rather than "tap" handlers, the touch events will not be fired consistently. I'm leaving this as is for now until I get a response from the Polymer team.

Comment 5 by sko...@chromium.org, Apr 20 2016

Labels: -M-51 M-52

Comment 6 by mfo...@chromium.org, Apr 22 2016

Labels: -M-52

Comment 7 by mfo...@chromium.org, May 12 2016

Cc: mfo...@chromium.org

Comment 8 by mfo...@chromium.org, Oct 26 2017

Status: Verified (was: ExternalDependency)
No longer repros for me on Chrome 63.

Sign in to add a comment