Chrome Version: 71.0.3569.0 (Official Build) fb87327b9e0a0a50c96e084943e5525c25f76fd1-refs/branch-heads/3569@{#1}(32/64-bit)

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

What steps will reproduce the problem?
1.Launch chrome and navigate to 'chrome://settings/content/notifications'.
2.Press tab key until focus reaches to first entry under 'Allow' section.
3.Press down arrow key such that focus travels to last entry.
4.Now click on 'Add' button under allow section and again press tab key.
5.Observe.

Actual Result:  Wrong focus navigation is seen after adding new entry under 'Allow' section on 'chrome://settings/content/notifications' page.
Expected Result: Focus should navigate properly after adding new entry under 'Allow' section on 'chrome://settings/content/notifications' page.

This is regression issue broken in ‘M-71’ and providing the bisect info below:
Good Build: 71.0.3558.0
Bad Build:  71.0.3559.0

Chromium bisect URL:

https://chromium.googlesource.com/chromium/src/+log/5bc7e0faee56286f64f9dd3f86f4e819a2557507..2465463e81a06ac8af33ed0be70e492413bfc523	

Suspect: https://chromium.googlesource.com/chromium/src/+/647d0eba90962cf3e070fc20fe9c5666f1e65000

@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.

Note:
1.Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect" error message.
2.Tried on other machines but still getting the same error again.
3.Hence provided suspect through 'Chromium bisect'

Kindly refer attached screen cast.

Thank You..!!

 

Deleted: Actaul Result.mp4 509 KB

	Actaul Result.mp4 509 KB View Download

Deleted: Expected Result.mp4 496 KB

	Expected Result.mp4 496 KB View Download