Correction:
This is a regression issue broken in 'M37' and reproducible on latest beta build i.e 51.0.2704.63 

Manual regression range:
Good Build: 37.0.2017.0 
Bad Build:  37.0.2019.0 

CL:
https://chromium.googlesource.com/chromium/src/+log/37.0.2017.0..37.0.2019.0?pretty=fuller&n=10000
(Unable to narrow down the range via tool bisect due to different UI in chromium builds)

Suspecting: 273183 or 273139 ?
Kindly help to re-assign, if your changes are not cause for this issue.

Deleted: Actual_Image.mov 7.8 MB

Actual_Image.mov 7.8 MB Download

Deleted: Expected_Image.mov 6.4 MB

Expected_Image.mov 6.4 MB Download

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Note:Above issue is still reproducible on latest canary version i.e 55.0.2878.0 (Official Build)

Deleted: Actual_Image.mp4 2.4 MB

	Actual_Image.mp4 2.4 MB View Download

Sorry for late response. It looks my patch does not affect print preview UI (The patch is for the image editor of Chrome OS)
gene@ - Could you take a look at this?

Bisected to https://chromium.googlesource.com/chromium/src/+log/67bfbce1a5b63fc56e5228e5711aa96882a3a08d..94fdfe5a7d1a2eac156abd9d4ab3ef8b34c48721 which has Blink roll 174924:174933.

The possible culprits are:
https://codereview.chromium.org/298023006
https://codereview.chromium.org/279763002
https://codereview.chromium.org/275913005
https://codereview.chromium.org/304453002

Bisect to https://codereview.chromium.org/275913005

drott, could you take a look? You're the author of that patch.

This is reproducible on Windows and Linux, the video above is recorded on Windows. My patch only applies to configuring font hinting on Mac and has no effect on Windows and Linux. thestig@, how did you identify this CL in your bisect?

I checked out r273208 on Linux, and a lot of hacks to make it build. Then I went through the Blink roll and tried the CLs in the roll until it failed.

Thanks. And when you revert it again, it starts working again? The only interaction I could imagine would be that the layout code incorrectly used the setUsePrinterFont flag on FontDescription for detecting a layout invalidation after returning from printing.

Mmmmhmm. If there's anything I can check for you, let me know.

Also,  bug 468683  sounds like a duplicate...

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

There is no longer any layout change in the main window when adjusting printing settings in the overlay.