Regression: Focus highlight is seen for both the options of 'Select source' in Cast overlay via tap/touch
Reported by
jshan...@etouch.net,
Jan 25 2017
|
|||||||||
Issue descriptionChrome Version:58.0.2992.0 (Official Build)25ff90033184e53f7fd47b44511397da29a1ce27-refs/heads/master@{#445908}-32/64 bit OS: Windows 10 (Touch device) Steps: 1. Launch Chrome and open 'Cast' overlay via context menu on NTP 2. Tap/touch on 'Cast to', then long tap/touch on 'Cast tab' and repeat the step 2 (refer video) 3. Observe Actual: Unnecessary focus highlight is seen on both the options of 'Select source' i.e on 'Cast tab' and 'Cast desktop' Expected: Focus highlight should not be seen on both the options of 'Select source' i.e 'Cast tab' and 'Cast desktop' This is a Regression issue broken in M-57,below is bisect info Good build:57.0.2974.0 Bad build:57.0.2975.0 Narrow bisect: https://chromium.googlesource.com/chromium/src/+log/0f17a6c232f6e4df227e3e149c6b097957151276..3963e231e4c43187a05f3c6420f5df997d734ea0?pretty=fuller&n=100 Suspecting: r442076 ? Please help to re-assign if your change is not the cause for this issue. Note: This is touch device specific issue, same works fine via mouse click.
,
Jan 25 2017
This isn't a regression you can reproduce this in M55 with the mouse as well. Mouse down on the "Cast Tab" item but with mouse depressed drag it over to the "Cast Destkop" and release. Notice you will get into the same state. The problem is the paper-item is setting a focused style on mouse down and not releasing it in certain scenarios like mouseleave. This is a problem with the cast overlay control. Unassigning myself; removing Release block stable since it is reproducible in M55 with mouse events.
,
Jan 25 2017
I don't think we customize the focus behavior for these paper-items so it may be a Polymer bug.
,
Jan 26 2017
,
Feb 9 2017
,
Feb 15 2017
,
May 10 2017
,
Jul 19 2017
This is reproducible on Windows, but not on Chrome OS (tested on Chromebook Pixel). So it seems to have to do with platform-specific ways in which touch inputs are sent to Chrome. I'm not sure if it's worth looking into any further.
,
Mar 30 2018
Won't fix in current UI. Future UI revamp should address.
,
Mar 31 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by nyerramilli@chromium.org
, Jan 25 2017