[User Feedback - Stable] Unexpected changes to DPI scaling |
||||||||||||
Issue descriptionChrome Version: 71.0.3578.80 OS Versions: Windows 10 Hey all, We're seeing user reports that the Chrome M71 update has changed DPI scaling preferences unexpectedly. Listnr: - https://listnr.corp.google.com/report/85827799630 - https://listnr.corp.google.com/report/85827564386 Community: - https://productforums.google.com/forum/#!topic/chrome/SCk1zy2uLYc reddit: - https://www.reddit.com/r/chrome/comments/a38k76/did_the_new_chrome_71_update_also_break_dpi/ User quotes: "I am using Windows 10 with 135% scaling at 1920x1080 resolution. with this new update everything looks smaller from the tabs , bookmarks bar , menu and even how the sites are displayed" "I use Windows font DPI 120 %, yesterday everything fine, today its too tiny" "1920x1080 no scalling but Chrome looks like 125%, i think they broke something" "Removing the parameters makes everything way too big and adding them makes the font from the tabs and bookmarks super tiny right now." There are references to a past parameter ("/high-dpi-support=1 /device-scale-factor=1 /force-device-scale-factor=1") that some users may have been using. Thanks!
,
Dec 5
,
Dec 6
,
Dec 6
Tested the issue on chrome reported version# 71.0.3578.80 using Windows-10 with steps mentioned below: 1) Launched chrome version# 70.0.3535.110 and made Resolution to 1920X1080, scaling to 125%(DPI machine) (no 135% DPI option available) 2) Added bookmark to bookmark bar, and updated chrome from Chrome://Setting/help 3) Chrome got upgraded to 71.0.3578.80, able to see all the text and bookmark(added in step-2) in normal font size Observations: Also tested the issue on Hi-DPI(Windows-10 surface pro, device pixel ratio: 2 ), even seen the same behavior as mentioned above Attaching the screencast of the testing performed. Thanks!
,
Dec 6
,
Dec 6
A few things: - 135% rounding down to 125% is as designed, to prevent our DIP-based layouts from becoming blurry or misaligning. - /high-dpi-support and /device-scale-factor are no longer working flags - /force-device-scale-factor flag is not supported (it's for debugging only) and is not in about:flags - 120% being "too small" is concerning. It may not be reproducible. But also note that there are several cases under which you have to test DPI: * All monitors set to 100% DPI on login, only one monitor then set to a higher DPI (test Chrome on both monitors) * Primary monitor set to higher DPI on login (may require log-out-log-in) and then one monitor set to high DPI (try both monitors), try Chrome on both monitors. * Note that Windows DPI settings are WEIRD and different things happen depending on whether the primary monitor was high-DPI when you last logged in! I'll have more info on the other reported issues shortly.
,
Dec 6
As expected, at 120%, Chrome scales to 125% (again, rounding to the nearest 25%). I cannot reproduce other behavior. People using the new Windows Text Scaling accessibility feature might also find that their window/text is larger than expected (this shipped with the most recent Windows update IIRC). Overall it doesn't look like there's anything there that is a regression caused by a supported feature. If we can reproduce the issue with the 4K monitor using the steps I've described above, or get reproduction instructions (was a monitor attached or removed during the sequence, for example?) then we should look at that more closely. As far as my group is concerned, there is no direct engineering action at this time, so passing back for more information collection.
,
Dec 6
,
Dec 7
same thing happened to me. When i updated chrome to latest version 71.0.3578.80 (Official Build) (64-bit), flags such as --force-device-scale-factor stopped working for me which is why i downgraded chrome to version 70. Everything was back to normal. Please fix the issue in the latest release. Thank You.
,
Dec 7
when I use 125% scaling everything is ok .. but I do not that scaling for my 1920x1080 resolution laptop 15.6 inch screen so I set the scaling to 135% but all sites in chrome version# 71.0.3578.80 look like the scaling is in 125% and not in 135%.. the result is that things displayed way too small compered too other browser like opera edge or firefox .. I would like to mention that this thing DID NOT happen in previews version of chrome .. please do something
thank you
,
Dec 7
Side by side of Chrome 71 and FF 63 this morning. Dell XPS 9570 in clamshell mode, running closed and plugged into HP Z27 4K Display running 150% Windows scaling in Ease of Access ("Make Everything Bigger"). Upgrading from 70->71 completely oversized every element of the app and all rendered sites. Nothing changed in regard to how I am running the display. It's been working fine on Chrome 70 and earlier with the same scaling settings for a very long time.
This happens when Chrome is already running and I plug the display in, or if I do a cold boot with the HP 4K monitor as the main (only, since the laptop is closed) display and launch Chrome after restart. Basically, Chrome 71 looks like this all the time regardless of the order of operations as far as plugging the display in, logging in, and or restarting the computer.
,
Dec 7
dfried@, could you ptal comments #9 to #12? Tentatively tagging as "RBS" for M71 for tracking purpose. Pls feel free to remove if needed.
,
Dec 8
I always started Chrome with this command in order to make it look like my other applications: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" /high-dpi-support=1 /device-scale-factor=1 Now that this doesn't work anymore with version 71 Chrome is a lot bigger than IE11. Attached file: Side by side comparison of Chrome 71 and Internet Explorer 11 (Windows 8.1 with 115% scaling).
,
Dec 11
Tested the issue on chrome reported version# 71.0.3578.80 using Windows-10 as per steps mentioned in C#14 1) Launched chrome version# 70.0.3535.110 from terminal with "/high-dpi-support=1 /device-scale-factor=1" 2) Made Resolution to 1920X1080, scaling to 125%(DPI machine) 3) Navigated to https://www.virtualbox.org, seen same behavior when compared with IE11 and chrome M-71, somehow doesn't reproduce the issue from TE's end, Attaching the screenshot of the testing performed. Thanks!
,
Dec 11
Friendly ping to look into this issue and to provide further update on this issue as it has been marked as a stable blocker. Thanks!
,
Dec 11
Regarding C#14: Sorry if this wasn't clear in my comment, I didn't use the flags "/high-dpi-support=1 /device-scale-factor=1" for my testing in C#14 because as per C#6 they "are no longer working flags". If I use these flags with Chrome 71, then - as another user already said in C#1 - it "makes the font from the tabs and bookmarks super tiny".
,
Dec 11
16: For now, I think we're safe to remove RBS. dfried@: Could you look at comments #9 to #12 when you have a chance? Thanks!
,
Dec 13
Removing "M71" labels based on #18.
,
Dec 14
I can confirm the issue on Version 71.0.3578.98 (Official Build) (64-bit) This is happening if custom scaling factor is set in Windows. I have, for example, set 114% scaling (System Settings > Display > Custom Scaling). See picture And unfortunately, Chrome becomes too big, because if I understood correctly, you are rounding it to 125%. And I have also tried with the flags: /high-dpi-support=1 /force-device-scale-factor=1 But, in that case everything is too small. Same as if I turn the custom scaling completely off. And if I change the numbers, I guess it's rounded again, eg. 1.1 behaves same as 1.0, and 1.14 behaves as 1.25 which isn't really acceptable. Previous version 70 worked OK.
,
Dec 17
craigtumblison@, Friendly ping to get an update as per C#20 as it is marked as RBS. Thanks..!
,
Dec 17
Removing RBS for now and assigning to dfried@ to take a look at some of the comments to see if any further action is needed. Thanks!
,
Dec 18
Comments 9-12, 14, 15, 20: As designed. The flags in question are not supported. Rounding to nearest 25% was a choice made to avoid rounding errors in DIP -> pixel layout. We may experiment with changing this in the future, but that should be a separate feature request. We made the decision with Windows Ease of Use Text Scaling to scale the entire browser, as individually scaling elements would have caused a number of serious visual artifacts. Again, probably worth revisiting at a future point but we should have a separate bug to track that as a feature request.
,
Dec 18
Comment 23 that is so sad .. you will force me to move to an none chromium browser.
,
Dec 18
Same for me. Every other browser on the market has this correctly implemented and now you make up new rules which don't make sense. As you have seen by the reported user feedback in many sources this makes the browser almost unusable, either everything is too big or too small. This is easily visible on 15in 1080p notebook screens. It was fine for previous 70 versions. Why the sudden change?
,
Dec 18
I have added issue #916276 to address flexible scaling outside of 25% multiples. This is going to require some development and a *lot* of testing on our end, so I've bounced up to product management for evaluation. Thank you for your feedback.
,
Dec 21
wow-Im havign same issues with text size etc.. someone fix this for us!
,
Dec 21
,
Dec 21
Please see the accompanying issue #916276 for updates to DPI and Text Zoom scaling issues. We are experimenting with a fix.
,
Jan 10
yet another arrogant response by Chrome team that it wont be fixed. It has become a trend off late. Pretty soon Firefox will catch up to Chrome and I will switch.
,
Jan 10
just now saw the update that it is blocked on the other defect. What puzzles me is why what exactly changed between v70 and v71? It was okay in v70 - but v71 it is messed up! What prompted this change that destroyed the scaling? and why not revert that change via a flag so it gives devs more time to adequately fix both issues (this one as well as the one that required the scaling change) |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Dec 5