Chrome Version: 70.0.3538.54 (Official Build) Revision 4f8e578b6680574714e9ed3bb9f02922b4dde40d-refs/branch-heads/3538@{#937} (32/64 Bit).

OS: Windows 10 (Touch Device).

Steps to reproduce:
1. Launch chrome, navigate to chrome://settings/Systems.
2. Disable Hardware Acceleration and relaunch chrome browser.
2. Try tap-touch on Minimize/Maximize/Close button in Chrome tab strip.
2. Observe .

Actual Result: Unable to Min/Max/Close browser via tap-touch.  
Expected Result: Should be able to Min/Max/Close browser via tap-touch. 

This is Regression Issue broken in M-68, and below is the bisect info.
Good Build: 68.0.3436.0 (Revision:560158)
Bad Build: 68.0.3437.0 (Revision:560453)

Narrow Bisect:

CHANGE-LOG URL:

https://chromium.googlesource.com/chromium/src/+log/7437045138faa8fb24b881a4a125555e775f8b2c..ff828877e7dd93fb123bc4d6539d93a2187334dd

Suspecting: r560353 ?

bsep@: 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. Issue is Win 10 (Touch Device) specific and is not seen on Win(7,8,8.1,10), Mac(10.12.6,10.13.1,10.13.6,10.14.1) and Linux(14.04 LTS) OS.
2. Unable to provide 'per-revision' bisect as it shows "RuntimeError : We don't have enough builds to bisect..." error message for above range. 
3. Hence provided suspect through 'Chromium bisect'.

Kindly refer the attached screen-cast.

Thank You!
 

Deleted: Actual Result.mp4 1.1 MB

	Actual Result.mp4 1.1 MB View Download

Deleted: Expected Result.mp4 1.5 MB

	Expected Result.mp4 1.5 MB View Download