Chrome Version : 70.0.3510.2 (Official Build) Revision 19bbe7b51081dd5aca29d10d5f881cce7eb95ff8-refs/branch-heads/3510@{#4} (32/64-bit)
OS: Windows 10 (Touch Device)

What steps will reproduce the problem?
(1) Launch chrome, navigate to chrome://settings/content page
(2) Now tap/touch on Flash option and observe while navigating page to flash page. 

Actual: Unnecessary focus highlight is seen while page navigating in chrome://settings/content.

Expected: No such a focus highlight should seen while page navigating in chrome://settings/content.

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..0dc78f92395b6c291a2a905f687ec77b914638ef?pretty=fuller&n=10

Suspect: r577743 ? 

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 do bisect per revision hence providing suspect from narrow bisect.
2) Issue is Touch specific and it is not seen on Click event.
3) Issue is not seen on Linux (14.04 LTS) and Mac (10.12.6, 10.13.1, 10.13.6, 10.14) OS.



Thank You!
 

Deleted: Actual_navigation.mp4 627 KB

	Actual_navigation.mp4 627 KB View Download

Deleted: Expected_naviagtion.mp4 346 KB

	Expected_naviagtion.mp4 346 KB View Download