Chrome Version: 72.0.3595.2 (Official Build) 4af8b5a14fa87ad1e81fa9ae20c30f9a8c1494cb-refs/branch-heads/3595@{#4}(32/64 bit)

OS:  Win(7,8,8.1,10) ,Mac(10.13.1 , 10.13.6 , 10.14.1)  and Linux(14.04 LTS)

Precondition: Atleast 2 entries should be present in 'chrome://settings/content/all' page.

Steps to reproduce:
1. Launch chrome and navigate to 'chrome://settings/content/all'.
2. Now press tab key until focus reaches to first entry and again press one tab key.
3. Observe.

Actual  : Focus does not travel on second entry on 'chrome://settings/content/all' after pressing tab key.
Expected: Focus does not travel on every entry on 'chrome://settings/content/all' after pressing tab key.

This is Regression issue seen in M-72, and will soon update other info.
Good Build: 72.0.3583.0
Bad Build: 72.0.3584.0

Chromium bisect info:

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

CHANGE-LOG URL:
  
https://chromium.googlesource.com/chromium/src/+log/62f2f8f209a82db0dd5a311eb4f844bddb75c98e..631a939b2b9a02a05cd1db367c7ea7fb17d14f50

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

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

Note:Tried per revision bisect on Windows ,Mac and Linux OS but unable to perform the same since getting "RuntimeError: We don't have enough builds to bisect" error 

Thank You

 

Deleted: Actual Result.mp4 271 KB

	Actual Result.mp4 271 KB View Download

Deleted: Expected Result.mp4 279 KB

	Expected Result.mp4 279 KB View Download