I might mention that if and when this bug is fixed, people like me who have adjusted to the new sense of the flag and toggled it already, in order to get back to using a browser that is not scaled by their OS, will need to toggle their flags AGAIN in order to fix their browsers being broken AGAIN after the fix.  These people will not be thrilled, but most of them will at least be able to figure out what to do.  This is probably an acceptable result.

If this bug is actually a feature, and this bizarre reversal of the sense of the flag is in fact intentional, then somebody should be smacked upside the head and the decision changed.

Allowing this to roll out to the stable release was a really painful error that negatively affects a lot of users.  If it were me, I'd put a rush on this fix, and perhaps even figure out how to pop up an "apology box" to the many thousands of negatively affected users (pretty much everybody who uses Windows 10's high DPI scaling) explaining what just happened to them.

Why did you enable this option in the first place?  If it was because Chrome appeared blurry (after being scaled by Windows), that should fix itself after logging out and logging back in to Windows.  If it was to make fonts smaller, can't that be configured in Chrome?

ivan, I find your question pointless.

I checked the box labeled "Disable display scaling on high DPI settings" in order to do what the name says, and not do Windows scaling on the Chrome browser.  There are lots of reasons to do things that way.   Until this week, it worked fine.   Now it's broken and does exactly what I told it not to do.   Rebooting did not make a difference.

Every Windows 10 user who has a scaling factor that is not 100% experienced an unexpected change in the behavior of Chrome this week:  the people who want scaling are now NOT getting it, and the people who do not want it ARE getting it.   

The good news is, if you just toggle your flag to the wrong value, you can get your correct behavior back.  LOL.

I'm seeing complaints all over the forums, and it looks to me that half the people who are believed to hate the new Material Design, really hate that their scaling was changed illogically due to this bug.

The Windows 10 scaling, when activated, changes every element of Chrome, including the sizes of tabs and other graphical elements that I don't know how to change back.  My personal complaint was mostly the loss of screen real estate when the non-webpage elements of Chrome ballooned 150% in size to correspond to my Windows scaling factor that I did not want to apply to Chrome.  The pages themselves are easily shrunk with control-minus.

A detail I didn't note before and should have: my Chrome is invoked by the shortcut target

"C:\Program Files (x86)\Google\Chrome\Application" /high-dpi-support=1 /force-device-scale-factor=1

And as I said, since version 53, I've had to leave the checkbox empty by the label "Disable display scaling on high DPI settings" in order to disable the scaling; and if I check the box, scaling is enabled.  This is the exact opposite of what it should do.  It did the right thing last week.  Rebooting makes no difference to any of this.

I see that the priority on this bug is 2 ("Want") but it's actually time sensitive and urgent (tens or hundreds of thousands of users negatively affected and wondering why Chrome looks weird now for them).   Can someone escalate it?  I don't see how to do it myself.

Oh, and the type should have been Bug-Regression.   Sorry, I'm new to Monorail.  

I've spent more time on this than I should, considering that I've already applied my own workaround.  I guess I'll just come back tomorrow and see if this train wreck, that has been going on for a couple of days without seeming to be correctly diagnosed, is starting to be correctly addressed.  Sigh.

Oh hey, thanks for connecting those emails, robliao.  I see from a quick search that my problem is probably a consequence of 

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

and, if so, will only occur for those people who have used the Windows startup flag /force-device-scale-factor .   Perhaps it's not as widespread as I feared, in that case, assuming that I was the one who added the flag and not the automated installer (my Chrome was first installed on this fresh Win10 system on 3/7/2016, judging by filesystem dates, with a 32" 4k monitor attached.  I don't recall the process I followed in disabling scaling for Chrome).

Expediting the bug fix, assuming the connection is valid, will address perhaps half of the dozens of complaints that we're seeing on forums, most of which are interpreted to be complaints about the Material UI, but are very likely the result of toggling the scaling flag from off to on (or vice versa) for all affected users.

--force-device-scale-factor is intended to be a development convenience and is not used by the automated installer for deployment.

Hi, Rob, thanks.  I really hope this problem is indeed narrower than I had feared, and only applies to people using an obscure flag.  Meanwhile, we'd better pursue it until we're sure.

I'm trying to isolate the flag problem.  Originally, my Chrome was invoked by the shortcut target
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" /high-dpi-support=1 /force-device-scale-factor=1
and I had the scaling disabled in Compatibility.  The behavior of this configuration changed suddenly and painfully this week, with the flag being inverted in sense.

However, if I remove either or both of these flags from the shortcut, or start Chrome directly from the exe file, I have not been able to get an unscaled Chrome with either setting of the flag "Disable display scaling on high DPI settings".  Rebooting does not change this.  Should I be using some other startup method, or some other method to get the non-webpage-elements of Chrome to be unscaled?   The flag is the obvious way, and it worked until last week, and now it's not working.

I'm not so much worried about my own configuration -- I can use my workaround -- but I'd like to have a "best answer" to give the dozen other people I've run across with the same problem over the past few days.

Thanks much.

Closing because we do not support the "Disable display scaling on high DPI settings" flag.

But just out of curiosity I tested this on 55.0.2866.0. With force-device-scale-factor=1, chrome renders at 100%, and without chrome renders at my native device scale (150% in this case). I also tested this on chrome 49.0.2573.1 and I got the same behavior. So yes, the setting doesn't do anything, but I'm not convinced it EVER did anything.

Not supporting that standard Windows flag is a really lousy idea.   A large fraction of Chrome users, after seeing that their default scaling isn't working well for them, will check this box and go "hey, what the heck, it's still zoomed."   Support the damn flag.

Also, there are instructions on the web that have become broken as of version 53.

Of the top seven hits for "chrome display scaling", #1 has a deprecated developer flag (becomes broken this week), #2 points to an unhelpful bug report, #3 suggests using the unsupported Windows flag, #4 points to a long and unhelpful bug report, #5 tells how to zoom web pages on a Chromebook, #6 suggests changing a 125% scaling to 126% if you want scaling, #7 has several solutions that don't work, and #8 suggests using the unsupported Windows flag.

<ahem>