Chrome Version: 71.0.3578.80 (Official Build) (2ac50e7249fbd55e6f517a28131605c9fb9fe897-refs/branch-heads/3578@{#860} (32/64 Bit)

OS: Windows(7,8,8.1,10)

What steps will reproduce the problem?
1. Launch chrome, go to chrome://settings/appearance and go to 'Customize fonts' sub-page.
2. Change 'Minimum font size' to Huge and open 'Report an issue overlay' from wrench menu.
3. Now, Close 'Report an issue' overlay overlay and change 'Minimum font size' to Tiny.
4. Again open 'Report an issue overlay' from wrench menu and observe the overlay.

Actual Result: Extra space is seen on 'Report an issue overlay' on second instance after changing font size to Huge.
Expected Result: No such extra space should be seen on changing font size to Huge for second instance.

This is a regression issue, broken in M-60 series, and below is the bisect info:

Good Build: 60.0.3074.0(Revision:465086)
Bad Build: 60.0.3076.0(Revision:465838)

CHANGE LOG URL:

https://chromium.googlesource.com/chromium/src/+log/60.0.3074.0..60.0.3076.0?pretty=fuller&n=10000

Suspecting: r465708 ? 

afakhry : 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.

Kindly refer the screen cast from the link given below

Note: 
1. Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect" error message for above range. (tried on other machines but still getting the same error again)
2. Unable to provide through Chromium bisect as 'Report an Issue' overlay is not seen on chromium builds.
3. Hence providing suspect manually.
4. Issue is not seen on Mac(10.13.1, 10.13.6, 10.14.2), Linux(14.04 LTS) OS.
5. Issue is also seen on Stable #70.0.3538.110, Dev #72.0.3622.0 and Canary 73.0.3629.0 build.

Thank You!

 

Deleted: Actual Result.mp4 928 KB

	Actual Result.mp4 928 KB View Download

Deleted: Expected Result.mp4 983 KB

	Expected Result.mp4 983 KB View Download