New issue
Advanced search Search tips

Issue 901841 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 896624
Owner:
Closed: Nov 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression
Team-Accessibility

Blocking:
issue 896748



Sign in to add a comment

Regression: Items in history list removed from keyboard tab order after one tabbing cycle

Project Member Reported by joanmari...@gmail.com, Nov 5

Issue description

Steps to reproduce:
1. Launch chromium/chrome canary
2. Enter history via platform keyboard shortcut (Ctrl+H, Cmd+Y)
3. Press the Tab key repeatedly

Expected results: Items in the history list (the checkbox, the page, the actions) would always be reachable by pressing the Tab key.

Actual results: items in the history list are initially reachable by pressing the Tab key. However, after one cycle of tabbing, the items are removed from the tab order.

Details after entering history initially:
 0. "Search history" (press Tab)
 1. "Chrome history" (press Tab)
 2. "Tabs from other devices" (press Tab)
 3. "Clear browsing data" (press Tab)
 4. checkbox to the left of a time stamp (press Tab)
 5. link for the page in history (press Tab)
 6. "actions"/three-dot popup menu (press Tab)
 7. "view site information" (press Tab)
 8. location/address bar: "chrome://history" (press Tab)

(End of first cycle)

 9. "Search history" (press Tab)
10. "Chrome history" (press Tab)
11. "Tabs from other devices" (press Tab)
12. "Clear browsing data" (press Tab)
13. "view site information" <-- FAILURE, should be the checkbox as above

At this point, Tab cannot be used to return focus to the list of items. This is a drag for people who rely on the keyboard and/or cannot use a mouse.

This problem does NOT occur for me with version 70.0.3538.77 (macOS and Linux).

This problem DOES occur for me in version 72.0.3599.0 (Linux, built locally) and 72.0.3602.0 (macOS, Canary Official Build).

 
Work around: Reloading the page (Ctrl+R or F5) makes the problem go away.
Components: UI>Accessibility
Labels: Needs-Bisect
Adding Needs-Bisect, as this sounds like a recent regression.
Cc: phanindra.mandapaka@chromium.org
Labels: -Type-Bug -Pri-3 -Needs-Bisect hasbisect-per-revision RegressedIn-72 Triaged-ET Target-72 M-72 FoundIn-72 Needs-Triage-M72 OS-Windows Pri-1 Type-Bug-Regression
Owner: dpa...@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue on the reported chrome 72.0.3602.0 and atest canary 72.0.3610.0 using Windows 10, Mac 10.14.0, Ubuntu 14.04. 
Below is the bisect information for same.

Bisect Info:
================
Good build: 72.0.3583.0
Bad build:  72.0.3584.0

CHANGELOG URL:
You are probably looking for a change made after 600224 (known good), but no later than 600225 (first known bad).
https://chromium.googlesource.com/chromium/src/+log/a1f14a1097fa402e72b99c5cab944b2d588bbc79..177774d57a744b75630cba5507c3bf1ed419aea3

Suspect: https://chromium.googlesource.com/chromium/src/+/177774d57a744b75630cba5507c3bf1ed419aea3

Reviewed-on: https://chromium-review.googlesource.com/c/1279191

dpapad: Please confirm the issue and help in re-assigning if it is not related to your change.

Thanks..!
Blocking: 896748
Cc: dpa...@chromium.org
Owner: rbpotter@chromium.org
I suspect that this is a duplicate of  issue 896624 .

@rbpotter: Can you verify?
Mergedinto: 896624
Status: Duplicate (was: Assigned)
yes, same issue. Merging.

Sign in to add a comment