Chrome Version: 72.0.3585.0 (Official Build) Revision	2eea43d10d3448c382da58fa116d4391f0d9db6d-refs/branch-heads/3585@{#1} (32/64-bit)
OS: Windows (7, 8, 8.1, 10), Mac (10.13.1, 10.13.6, 10.14.1) and Linux (14.04 LTS)
 
What steps will reproduce the problem?
1. Launch Chrome, give print command and enter invalid text under pages option.
2. Press tab key to traverse focus and observe. 

Actual  : Focus does not traverse in sequence on pressing tab.
Expected: Focus should traverse in sequence on pressing tab.

This is a regression issue, broken in M-72 series, below is chromium bisect info:

Good build: 72.0.3583.0 (Revision: 600164)
Bad build : 72.0.3584.0 (Revision: 600616)

You are probably looking for a change made after 600217 (known good), but no later than 600225 (first known bad).
CHANGE-LOG URL:
https://chromium.googlesource.com/chromium/src/+log/7e3361f0a1f2962a85c8cf36b6ea2f403328419e..177774d57a744b75630cba5507c3bf1ed419aea3

Suspecting: https://chromium.googlesource.com/chromium/src/+/62f2f8f209a82db0dd5a311eb4f844bddb75c98e

@xlou: 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. Provided suspect through 'Chromium bisect' script because unable to perform bisect using 'per-revision' bisect script.
2. Tried performing 'per revision' bisect on multiple Windows and Mac machines but unable to perform the same since getting "RuntimeError: We don't have enough builds to bisect." error.

Kindly review the attached screen-cast for reference.

Thank you.
 

Deleted: Actual_Result.mov 1.8 MB

	Actual_Result.mov 1.8 MB View Download

Deleted: Expected_Result.mov 1.6 MB

	Expected_Result.mov 1.6 MB View Download