Issue metadata
Sign in to add a comment
|
Regression: Focus gets stuck on Number field for second instance.
Reported by
jshan...@etouch.net,
Mar 17 2016
|
||||||||||||||||||||||
Issue descriptionChrome Version: 51.0.2681.0 (Official Build)2668bea689fd4a5ce07011903bca095aaf67bb07-refs/heads/master@{#381614} 64-bit. OS: Mac URL: https://www.msu.edu/~urban/sme865/resources/embedded_pdf.html Steps: 1. Launch Chrome, navigate to above URL and click on download button of embedded pdf. 2. Now go to chrome://downloads, and click on grey link under downloaded pdf. 3. Press tab key and observe the focus traverse. Actual: Focus gets stuck on Number field for second instance. Expected: Focus should not get stuck on Number field for second instance.(i.e it should be seen on tab strip after traversing on page) This is a regression issue broken in M-49, below is bisect info Good build: 49.0.2570.0 Bad build: 49.0.2571.0 Narrow bisect: https://chromium.googlesource.com/chromium/src/+log/44d232c33e46199f9247a68bd6cc368374367c16..a733413f04c4cf1859f013f67fdd2cdfa13fb286?pretty=fuller&n=100 Suspecting: r360980 ? Please help to reassign if your change is not the cause. Note: This is a Mac specific issue not seen on other OS like Windows and Linux.
,
Mar 19 2016
I took a look at this and could repro locally. My r360980 reverted part of the behavior I introduced in an earlier CL, r357011 (or rather its reland in r358207), so I wasn't expecting it to cause this. However, trying this out, it seems that my r357011 might have inadvertently fixed this behavior, and then r360980 reverted that fix (because it broke other things). I've randomly tried a build for r356974, which was before any of my changes, and this is still broken in that build. So I don't believe my CLs ultimately are responsible for this. Could you run the bisect on versions <= 48.0.2550.0, which is before my r357011?
,
Apr 14 2016
,
Apr 14 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 20 2017
I think this is now magically fixed. Please reopen if I'm wrong. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kroot@chromium.org
, Mar 17 2016