DOM element that appears in tapped location becomes focused.
Reported by
jshan...@etouch.net,
Mar 30 2016
|
||||||||
Issue descriptionChrome 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.
,
Mar 30 2016
,
Apr 2 2016
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.
,
Apr 4 2016
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.
,
Apr 20 2016
,
Apr 22 2016
,
May 12 2016
,
Oct 26 2017
No longer repros for me on Chrome 63. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by jshan...@etouch.net
, Mar 30 2016Labels: Proj-Windows10 hasbisect
Owner: apaci...@chromium.org
Status: Assigned (was: Unconfirmed)