New issue
Advanced search Search tips

Issue 877891 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 878331
Owner:
Closed: Aug 29
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Focus does not travel to 'more actions' icon on pressing tab key.

Reported by pranjali...@etouch.net, Aug 27

Issue description

Chrome version : 70.0.3534.0 (Official Build)  68a5d485789e45a91c9fa90aab4dd33113131ccd-refs/branch-heads/3534@{#1}(32/64 bit)

OS:  Windows(7,8,8.1.10) ,Linux(14.04 LTS)  and Mac(10.12.6 , 10.13.1 , 10.13.6 , 10.14).

What steps will reproduce the problem?
1.Launch chrome and navigate to ' chrome://settings/content/notifications'.
2. Add any site under 'Allow'  section (i.e Allow notification for site ).
3. Now press tab key to bring focus on added site and observe.

Actual  : Focus does not travel to 'more actions' icon on pressing tab key  in ' chrome://settings/content/notifications'
Expected: Focus does not travel to 'more actions' icon on pressing tab key in' chrome://settings/content/notifications'

This is a regression issue broken in ‘M-70’ and using per-revision bisect providing the bisect results,
Good Build : 70.0.3501.0
Bad Build: 70.0.3502.0

You are probably looking for a change made after 577742 (known good), but no later than 577743 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/b3d2f01439976295d1a529f29f2dd7ebe4482caf..fc566d1c1a2d8da82ccce610b153f3b54524eab4

Suspect: https://chromium.googlesource.com/chromium/src/+/fc566d1c1a2d8da82ccce610b153f3b54524eab4

aee@Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thank You!


 
Expected Result.mp4
270 KB View Download
Actual Result.mp4
423 KB View Download
Mergedinto: 878331
Status: Duplicate (was: Assigned)
This is due to the icon being able to gain focus instead of the parent cr-policy-pref-indicator. I'm fixing this in another issue.

Sign in to add a comment