This was broken when enable-per-monitor-dpi was made default.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d361a071345fb793ee74671cd9660162841dacf1

commit d361a071345fb793ee74671cd9660162841dacf1
Author: robliao <robliao@chromium.org>
Date: Wed Jul 27 02:03:42 2016

Allow Forced Scale Factor with Per-Monitor DPI

BUG= 631829 

Review-Url: https://codereview.chromium.org/2176183005
Cr-Commit-Position: refs/heads/master@{#408013}

[modify] https://crrev.com/d361a071345fb793ee74671cd9660162841dacf1/ui/display/win/screen_win.cc

My recent problem report, rolled out to the STABLE VERSION (yikes), is likely a result of this bug.

https://bugs.chromium.org/p/chromium/issues/detail?id=648082

If so, this fix must be given a super super high priority, because every user who is using the startup flag will have had their display scaling flag toggled upon the rollout of version 53.  I'm seeing dozens of complaints about the Material UI on forums, and many of them are likely to actually be complaints about this bug.

I'm an end user, who is a former programmer but whose work should be triple checked.  :)   Best of luck and thanks.

In my other thread, robliao says that the automated installer has never used the force-device-scale-factor flag.  So, I figure the problem is likely to apply only to a few dozens, not many thousands, of users.

Yayyyy.   I'll pursue it for the sake of the dozens of us affected, but the full-on fire drill is put on hold while we verify the limited nature of the problem.

Cheers
Marc