Regression: Default focus is seen missing in chrome://settings/content on mouse click |
|||||
Issue descriptionChrome Version:60.0.3112.40 OS:Ubuntu 14.04, Windows What steps will reproduce the problem? (1)Launch chrome and navigate to chrome://settings/content (2)Click on PDF documents and then click on back button (3)Observe the PDF documents button Expected: Focus should be seen on PDF documents button Actual: Instead, Focus is not PDF documents button This is a Regression issue broken in M-60 Will update other info soon..
,
Jun 21 2017
Manual Bisect Info: =================== Good Build:60.0.3078.0 Bad Build: 60.0.3079.0
,
Jun 21 2017
Using the per-revision bisect providing the bisect results, Good build: 60.0.3078.0 (Revision: 466494). Bad build : 60.0.3079.0 (Revision: 466571). You are probably looking for a change made after 466518 (known good), but no later than 466519 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/fbf1af2f99e4361b23ec0618c4faf75042b66cfc..1a5de509094aed3724a71314771f70a01a0584f8 @dbeam: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner. Thank You.
,
Jun 21 2017
Are you sure the focus is missing? Or is it just that we don't show the ripple? In other words, what happens when you press Tab? Does focus continue to the element right after the "PDF documents" button? I suspect that this is WAI.
,
Jun 23 2017
see above ^
,
Jun 27 2017
As per Comment #4, please find my observation. In Chrome Good Builds -- Clicking on PDF Documents and navigating back, the focus is seen near the PDF Documents. In Chrome Bad Builds -- Clicking on PDF Documents and navigating back, the focus is not seen near the PDF Documents. Re-assigning to the owner for further update. Thank You.
,
Jun 27 2017
This is working as intended. The focus is not "seen", because we don't want to show the ripple, but the focus is at the correct position when exiting the "PDF documents" subpage (see crbug.com/716184 for details).
,
Jun 28 2017
Issue 737426 has been merged into this issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jun 21 2017Status: Untriaged (was: Unconfirmed)