Windows --high-dpi-support flag is going away - Now use the registry.

[Eugene Girard]

With recent changes to chrome, the high-dpi flag is no longer working. It has been removed as of r256811. High dpi support is now controlled by a registry setting stored in [HKEY_CURRENT_USER\Software\Google\Chrome\Profile]. The flag is called "high-dpi-support" and is a DWORD. The flag can be set to "0" (disabled), "1" (enabled) and "2" (default). If the setting is not found, then it defaults to "2"/default, which for now means the same as disabled.

You can also use the attached reg files to change settings.

Why the change? Briefly, the OS needs us to call SetProcessDpiAwareness/SetProcessDPIAware very early in the run, before we've initialized things like profiles and settings. Thus, we can't read the value in chrome://flags.

[Alex Sorokoletov]

Dear Eugene,

The files are not opening because of UTF-8 encoding and some trailing characters. Resaving them in ANSI helped.

However this flag is kind-of-working on latest Chromium build for Windows (36.0.1941.0 (Developer Build 263732))

Kind of, because it's rendering really nice. Like it's Safari and MacBook Pro Retina. 

Unfortunately, for document height and width the app takes original screen size (2560x1600 in my case) and I actually can see only left-top part of the website.

I can not see the menu button (which is in the url address bar placed in rightmost angle).

Would be great if you can look into it and fix it so we can continue enjoying Chromium.

Thank you.

четверг, 13 марта 2014 г., 15:13:33 UTC-4 пользователь Eugene Girard написал:

[Alex Sorokoletov]

Found that the issue is already filed:

https://code.google.com/p/chromium/issues/detail?id=363289&q=dpi&colspec=ID%20Pri%20M%20Iteration%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified

понедельник, 14 апреля 2014 г., 22:41:23 UTC-4 пользователь Alex Sorokoletov написал:

[Damon Spiegel]

I'm running Windwos 8.1 and today on a reboot i lost my DPI settings. I have searched the registry but don't have the key mentioned within my reg nor do i even have a profile key.  Under chrome i have BLbeacon, BrowserCrash and Metro. Any suggestions?

[Scott Graham]

I think you can probably just make the key and value, but I'm not sure
why it would have disappeared.

> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev

[Damon Spiegel]

Hi Scott,

 

Thanks. I just created the key and while the appearance is somewhat back the tabs and bookmark bars are somewhat blurry (like it was 6 months ago before support for it was available.).

 

Any ideas on how to make it crisp looking again?

[Willy]

Same thing happened to me by the way, Chrome pretty much unusable since today...

[jarp53]

sorry to be a bother but i don't know how to make the key; so i got as far as ....\profile  what to do next 

[jarp53]

it did not let me change the name 

[Damon Spiegel]

Hey Jarp53, I had the same issue and then i downloaded a file and it created it for me...I've uploaded it here for you to download. hopefully it works for you as well. Let tell you know that going through all of this and getting high dpi support hasn't really make it any more usable. the zoom is at 150 on every new page, the bookmarks are blury, etc etc.

Please let me know once you've download this so i can take it offline.

thanks,

https://onedrive.live.com/redir?resid=950BC5789D5C6FB0%2152787

[PeterO]

The files here are not working with the latest dev channel which is 64 bit.

In the article here http://code.ecomerc.com/Articles/ChromeHIDPI/

It is described that you need another key in a WOW64 bit node, in the article there is also a download link for an updated registry file.

Regards

Peter

[Makerender]

I managed to fix it with the registry from this link http://code.ecomerc.com/Articles/ChromeHIDPI/ 

[T.Das777]

Everytime i change the value of HKEY_CURRENT_USER\Software\Google\Chrome\Profile\high-dpi-support to 1, after starting chrome, the value reset to 2 automatically.

Anyone has experienced this?

[akta...@gmail.com]

Yes. I manually changed the registry keyword to "1" and reopened Chrome and the DWORD value had reset to 2.

[Jonathan Curro]

I'm afraid to report that I too have this problem on an original MS Surface Pro running Windows 8.1, and Chrome Version 36.0.1985.125 m. This makes me deeply sad... If anyone hears of a change to this issue please post. 

Thanks all.

[oshima]

maybe crbug.com/393050?

--

[Shrikant Kelkar]

Thanks Oshima,

Yes, this should should have been fixed in release 37.

[Liran Barniv]

The registry entry high-dbi-support dword 1 , is no longer working.

I was able to work the magic but is stopped working about a week ago.

[David Gila]

Thanks a lot! It worked in Windows 7.

[Donald Newlands]

Yep! The value goes back to 2 every time I restart Chrome.  (Surface Pro 3/Windows 8.1) However, I'm getting full resolution now after disabling scaling in compatibility and after switching from desktop mode to Windows 8 mode and back again.

Too bad the tabs don't scale with the page window -- they're too small to read now. 

[Amrit Orie]

This registry fix was not working for me because the high-dpi-support value was getting reset to 2 every time Chrome was launched. Adding /high-dpi-support=1 /force-device-scale-factor=1 as launch parameters for chrome as described here, worked for me. It's basically a hack but I don't care as long as it works. Your Chrome shortcut target should be 

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

if Chrome was installed in the default location.

[Chad Murphy]

That also worked for me. I noticed that in chrome://flags the #force-device-scale-factor is not available to me but it seems to work when passed as a startup flag as below.

[PhistucK]

This way of specifying flags is very strange. Why would / work as a flag prefix?

☆PhistucK

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Torne (Richard Coles)]

On windows / is accepted as well as --, see https://code.google.com/p/chromium/codesearch#chromium/src/base/command_line.h&l=56 and related.

That's the usual way of specifying flags to commands on windows so I imagine we implemented it just in case people misinterpret instructions that say "set the foo flag" as meaning /foo.

[PhistucK]

Interesting. Thank you for the (really) prompt reply!

☆PhistucK