New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 649238 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:[MD-History] Focus does not travels properly after pressing 'Tab' key.

Reported by dmascare...@etouch.net, Sep 22 2016

Issue description

Chrome Version:55.0.2868.0 (Official Build) b22235a16193be6cfa6e199a5c7a2427a7b505e6-refs/heads/master@{#420217}
OS: Windows(7,8,10)

What steps will reproduce the problem?
1. Launch chrome and visit any web page to generate some history.
2. Go to chrome://history page, press 'Tab' key from keyboard such that focus reaches to iron icon of 1st url.
3. Again press 'Tab' and observe.

Actual: Focus does not move to 2nd url.
Expected: Focus should travel on all checkbox/URL/more option icon present on history page

This is regression issue, broken in 'M 55' and will soon update the bisect info:

Good build:55.0.2867.0
Bad build:55.0.2868.0

Note: Will soon update Mac and Linux OS info.

 
Actual_history.mp4
900 KB View Download
Expected_history.mp4
486 KB View Download
Labels: OS-Linux OS-Mac
Note: Above issue is reproducible on Mac and Linux OS
Labels: ReleaseBlock-Stable hasbisect-per-revision
Owner: calamity@chromium.org
Status: Assigned (was: Unconfirmed)
CL:

https://chromium.googlesource.com/chromium/src/+log/eedb95b1a034bb392ed83e84ee690395a0db3e27..a1bc7bb78d1a777435f8aa73bdcd4eaae4eff8b3

suspecting, https://chromium.googlesource.com/chromium/src/+/a1bc7bb78d1a777435f8aa73bdcd4eaae4eff8b3
calamity@, could you please check the issue.

As this is recent regression adding RB label, please change if required.

Comment 3 by ajha@chromium.org, Sep 28 2016

Cc: dbeam@chromium.org
calamity@: Could you please take a look at this issue and update the thread.

Comment 4 by dbeam@chromium.org, Sep 28 2016

pretttty sure this is what we want.
Status: WontFix (was: Assigned)
This matches the behavior of the old history, as intended.

Sign in to add a comment