New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 404 users

Comments by non-members will not trigger notification emails to users who starred this issue.

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 2014
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug


Sign in to add a comment

Enable high-DPI support in Vista, Win7 and Win8

Reported by anthony....@gmail.com, Sep 17 2012

Issue description

Chrome Version       : 23.0.1262.0
OS Version: 6.2 (Windows 8) 
Other browsers tested:
     IE 10: OK

What steps will reproduce the problem?
1. Open Chrome
2. Open IE
3. Look at the difference between the fonts on any given site

What is the expected result?
When running Windows 8 under Bootcamp on a MacBook Pro Retina, I expect the fonts in Chrome to be as sharp as those in IE10.

What happens instead?
The fonts in Chrome are hard to read and fuzzy.

I have attached a screen shot. Also if it helps, it looks like this is/was a known issue for the OSX side of things (http://www.hongkiat.com/blog/mbp-retina-blurry-text/ and http://chrome.blogspot.com.au/2012/06/chrome-and-new-shiny.html) but the windows side of things still seems to be having problems. 

UserAgentString: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.10 (KHTML, like Gecko) Chrome/23.0.1262.0 Safari/537.10


 
BootcampWin8ChromeVsIE.PNG
716 KB View Download
Showing comments 137 - 236 of 236 Older
Hidpi support in Chrome 34 is indeed better, thanks for the instructions.

Still, there are some troubles:

1) some extension icons are not visible in the toolbar. There is a button with no icon or so for some extensions (e.g. pocket: https://chrome.google.com/webstore/detail/pocket-formerly-read-it-l/niloccemoadcdkdjlinkgdfekeahmflj/related )

2) in the download toolbar, file format icons are too big 

3) plugins don't work properly. "aw snap" when opening internal pdf viewer, and external plugins (Adobe PDF or Adobe Flash) don't scale up and are only about a quarter of the size it should be.

I don't know whether all this is filed somewhere...
Image 2014-01-14 at 8.16.48 AM.png
3.5 KB View Download
Image 2014-01-14 at 8.15.36 AM.png
9.0 KB View Download
I experience the same problems as in #137.

No extension icons visible for OneTab, QR-Code Extension, Chrome UA Spoofer and even the Google internal PageSpeed Insights extension.

But 2) and 3) are much more urgent. Hopefully they will be fixed soon.

But thanks anyway for the update.
You forgot the Flash player. On every site with flash (not sure if its only a flash problem) I get very often "Site not responding. Quit or wait" notifications. And if I click wait it pops up again after some seconds and if I click quit I get this "aw snap".

Comment 141 by men...@gmail.com, Jan 15 2014

> So here is the deal, we have disabled hidpi on m32 as to not get people stuck in things like you see in #128.

Don't think it worked though. My stable Chrome just got updated to m32, and it was totally broken.
I got it unstuck using advice from 
https://code.google.com/p/chromium/issues/detail?id=160457#c51
I have the same problem that was reported in  Issue 329343  and the product forums (with screenshot:  http://productforums.google.com/forum/#!topic/chrome/1tkrKVZTiDw) which is related to incorrect handling of high DPI settings in Chrome 32 (on a Surface Pro).  It is completely unusable in Metro mode and the text is blurry in desktop mode so I was forced to switch to a different browser.
Using v34 Canary and the hidpi switch the text still seems a bit fuzzy to me compared to compatibility mode on v32.

Unboxed my Dell XPS15 Windows8.1 (3200x1800) this morning and first ran into the bunched up tabs issue and then found this and noticed the fuzzy text.

Also running v34 with the hidpi switch:
- I'm unable to resize the chrome window.
- I can resize the extension button area and click the "sort bookmarks ext" and it works, just can't see the green arrow icon, the "wait and done" icon overlays do show up though.

Hope this is sorted out soon, thanks :)

[installing 600MB worth of Windows updates, though I doubt any of these will impact on this issue as it seems to be fairly evident (from this thread) that Chrome simply doesn't deal well with this env yet.]
chrome_hidpi.png
571 KB View Download
also the obvious work around for this which I didn't see in this thread is to simply go native.

right click the desktop, screen resolution.
make text and other items larger or smaller.
tick the box "let me choose one scaling level for all my displays"
select smaller 100%
apply
log out / login

of course this makes everything small (as it is 1 pixel = 1 pixel, no funny business), however it is all crisp and works 100% until this is resolved. 
In the last 4 canary versions Chrome was very laggy. So I removed my profile and hoped it would work better with a new one...
In the current version hidpi didn't enable. But after many restarts and many new profiles (tried the flag again in between => didn't work). HiDPI works again now. But the extension icons disappeared again. This was already fixed in the versions before.

But everything except the reload and home icon seams very crisp now.

The 3 problems mentioned earlier (PDF, ...) are still there. 
Okay and the bad news: Loading sites is still very slow and scrolling on them laggs really. I have to wait about 5s to be able to scroll for 2s and then wait again etc. I am sure it isn't the hardware (XPS 15 9530).
Again forced to use Firefox. :(
I have the same issue here. Got a 1920x1080 screen on 17", the Windows UI is set to 125% but chrome stays 100%. 
The chrome://flags HiDpi enable setting appears to work as designed on Chrome 32.0.1700.107 m on my Lenovo Ideapad Yoga 2 Pro running Windows 8.1.

However I've noticed text kerning appears to be slightly off. But I'm glad to see progress.
Blocking: chromium:143619

Comment 150 Deleted

The hidpi flag works again now, but there are still no extension icons visible and the scroll bars are very huge.
Is still someone working on this? :/

Comment 152 by Deleted ...@, Feb 15 2014

The high dpi flag stopped working for me on more recent Canary builds, both the flag in chrome://flags and --high-dpi-support=1 on the shortcut won't enable it.

Dell XPS 15 9530 - Windows 8.1

Comment 153 by Deleted ...@, Mar 6 2014

On the new retina under bootcamp, chrome still is very blury compared to IE, menus, window, text in dialogs etc, all look bit out of focus, and this is with highdpi enabled. Chrome is one of the best browsers out there... except for retina displays, which is a pitty. Webpages renders unsharp often too, especially drop downs and buttons, but I'm unsure if this is the webpage design or the browser. 

Macbook Pro Retina, Chrome Version 33.0.1750.146 m
The "enable high dpi" flag stopped working under windows 8.1.
what happened?!

Comment 155 by Deleted ...@, Mar 9 2014

HiDpi still works for me.
But extensions icons, scrollbars, ... are not fixed yet.
What is taking so long? :(
Project Member

Comment 156 by bugdroid1@chromium.org, Mar 13 2014

------------------------------------------------------------------------
r256811 | girard@chromium.org | 2014-03-13T13:17:44.976579Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/win/dpi.cc?r1=256811&r2=256810&pathrev=256811
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/generated_resources.grd?r1=256811&r2=256810&pathrev=256811
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_browsertest.cc?r1=256811&r2=256810&pathrev=256811
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/win/dpi.h?r1=256811&r2=256810&pathrev=256811
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/about_flags.cc?r1=256811&r2=256810&pathrev=256811

Move supports-high-dpi flag into registry.

Calls to SetProcessDpiAwareness need to happen immediately when the app starts. Specifically, before user profile settings have been initialized.

This patch moves the --supports-high-dpi into the registry.

BUG= 339152 ,  149881 ,  160457 

Review URL: https://codereview.chromium.org/153403003
------------------------------------------------------------------------
I want to add that MultiDpi doesn't work at all. On the high-dpi screen it works (with all the mentioned bugs) and on the lower dpi screen everything is unbelievable huge. If you need some screenshots, I am glad to help.
RE: #157
When you say MultiDpi, do you mean Win8.1?
Yes. Win 8.1 with one 3200x1600 (15") display and one 1920x10ß80 (24") display.
Cc: -pkotw...@chromium.org
In the latest few canary versions it is completely broken. The flag is gone and the "--supports-high-dpi / --high-dpi-support=1" doesn't work either. :(
Again forved to used Firefox...
RE #161: 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.

I've posted a reg file that will enable or disable the registry setting directly. See
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/U_K1NHuMLic
RE: #162: In HKEY_CURRENT_USER\Software\Google\Chrome\ is no folder called Profile. Should I create it or is it the wrong place?
RE: #163 - The folder probably doesn't exist (yet). Create it, or use the reg scripts.
The reg script doesn't work. But after creating it manually it works like a charm. Only one bug found yet. You can't move a single tab in another window like earlier.
If you can automate the install process in future and fix the last bug it will be perfect.
Thank you very very much!
RE #165: The tab moving issue is probably fixed by  Issue 346825 
Google are just forcing every new laptop owner to use Firefox, how is this still not fixed?
You can finally enable it with that registry key, but pay special attention to text on facebook for example.  For me, the letters of the words "News Feed" are too close together.
Capture.PNG
3.8 KB View Download
RE #168: We are working on this as part of  Issue 25541 
So.. Firefox it is then. It was nice knowing you Google Chrome.
Why did you re-enable 'Relaunch Chrome in Windows 8 Mode' if hidpi is still messed up in latest 34.0.1847.116 m stable I got today? Again the window was very tiny in Windows 8 mode and I couldn't access the menu anymore so I lowered my resolution to access the menu and relaunch in Desktop mode. With everything still fuzzy obviously.
Confirming #165: setting the registry key to 1 enables high dpi, which looks great. But it becomes impossible to drag the Chrome window or to drag individual tabs.

This is on the just-released Windows 8.1 Update 1, using a Samsung ultrabook with 3200x1800 display.

The registry key does not seem to work on 34.0.1847.116 m.
RE #173: What os version are you running? desktop/metro? resolution you expect?
RE #174: Windows 8.1 64bit with Update 1. Desktop mode. I am running 3200 x 1800 on a Dell XPS 15. Registry key on/off yields no difference. And anyway you can clearly see the difference with IE and Firefox.
hey #175 chrome doesn't work yet in any mode or switches etc
I've gotten around it by going native, as I said in #144

hope chrome catches up though :)

Comment 177 by Deleted ...@, Apr 11 2014

You are losing this battle, guys.

I have used Chrome for years. I recently bought a dell with QHD laptop and I had to switch to IE 11. Microsoft does it really well (I write from IE).
I would like to continue using Chrome, for its versatility and for conviction BUT its getting late. 
You should take more care about it. You introduced Chrome as a way to speed up web evolution and experience improvement; we adopted it as a revolution. Now you are not that experience nor that revolution on HD screens.

People asked you to solve this a lot of years ago. 

If you don't care then we don't care.

Thanks for your attention.

(Dell Precision M3800 - QHD+ 3200x1800 - Windows 8)

Comment 178 by Deleted ...@, Apr 14 2014

There is still a problem with enabling the high dpi setting in the registry. The font spacing gets all crazy after doing this. Letters will be either squished together or some are far apart. Very disappointing and distracting. Hopefully this gets fixed!
Blockedon: chromium:25541
RE #178: Font spacing will be fixed as part of  issue 25541 

Comment 180 by Deleted ...@, Apr 15 2014

I'm using a Macbook Pro running 8.1. I am having the same issue and my registry does not show these options. Under Chrome, I see BLBeacon, BrowserCashDumpAttempts, and Metro, nothing for dpi. This fix is unavailable to me.

Comment 181 by Deleted ...@, Apr 17 2014

Lenovo Yoga 2 Pro with windows 8.1 patch 1. Same issue. 

Comment 182 Deleted

Comment 183 Deleted

Comment 184 Deleted

Used the flag since it was introduced without issues, but the registry setting does not appear to do anything on my end. I'm stuck with pixelated chrome. Tried setting the same setting under Wow6432Node since Chrome is 32-bit, but that didn't help either.

Version: 34.0.1847.131 m
blob.png
300 KB View Download
The issue has been resolved in latest Dev build Chrome 36. Confirmed to be working on Lenovo Yoga 2 Pro.
its working for me using Chrome 36 Dev version 
also you must use the provided registry file in this topic to enable High DPI as in Version 36 the option is not available in the flags page 
Untitled picture.png
408 KB View Download
RE: #185 same for me for the registry key but it works fine on the beta and dev channels. I am using the beta channel now as it is theoretically more stable than the dev one.
Re #186: I wouldn't call it "resolved" as the current method is still just doubling pixels in order to scale larger, rather than supporting the scaling natively. This issue won't be resolved until native scaling and DirectWrite are implemented: https://code.google.com/p/chromium/issues/detail?id=25541
RE #172L Same problem. A bit annoying that I can't use the title bar.

Comment 191 by Deleted ...@, May 23 2014

I had chrome sharp but with text spacing issues, until today.

It's just launched with tiny top bars, and by enabling Touch UI I can get the bas proper sized, but with seriously blurry text.

Yet others are saying it's fixed? How do I fix mine?
Project Member

Comment 192 by bugdroid1@chromium.org, May 24 2014

------------------------------------------------------------------
r272721 | ananta@chromium.org | 2014-05-24T12:44:42.259212Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/history/select_favicon_frames_unittest.cc?r1=272721&r2=272720&pathrev=272721
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/layout_unittest.cc?r1=272721&r2=272720&pathrev=272721
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/extension_icon_image_unittest.cc?r1=272721&r2=272720&pathrev=272721
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/layout.cc?r1=272721&r2=272720&pathrev=272721
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/test/run_all_unittests.cc?r1=272721&r2=272720&pathrev=272721
   M http://src.chromium.org/viewvc/chrome/trunk/src/components/favicon_base/select_favicon_frames.cc?r1=272721&r2=272720&pathrev=272721
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_process_host_impl.cc?r1=272721&r2=272720&pathrev=272721
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/resource/resource_bundle_unittest.cc?r1=272721&r2=272720&pathrev=272721

This is in preparation for enabling HiDPI on Windows by default. Most of the changes here are replacing usage of
the ui::GetImageScale function with ui::GetScaleForScaleFactor.

The patch to remove the HiDPI switch and enable it by default will follow. This patch has been incorporated from
girard's patch ( https://codereview.chromium.org/232483005/)

BUG= 149881 ,  362245 

Review URL: https://codereview.chromium.org/294863002
-----------------------------------------------------------------
Enabled HighDPI flag in registry and appears to be workin (apart from a couple bugs I've seen files already). One behavior I've noticed that I haven't seen mentioned yet is that dragging from a HighDPI monitor to a 100% scaling monitor results in blurry downscaling, indicating the windows 8.1 hooks for multi-monitor, multi-dpi support haven't been implemented yet.

Comment 194 by Deleted ...@, May 25 2014

Yep, I just followed the solution that was posted here: 
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/U_K1NHuMLic

And everything now is crystal clear just like I wanted it to be. Basically, all you have to do is:
1. Update to Google Chrome 36 or 37: http://filehippo.com/download_google_chrome/
2. Download the .reg file in the Google Groups link above and add it to your registry.

I'm so happy there's finally at least some sort of solution.
Project Member

Comment 196 by bugdroid1@chromium.org, May 28 2014

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

commit 89318bec6014e7627c32fe6dfcd8759d340d331a
Author: ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Wed May 28 13:59:45 2014

Enable --high-dpi-support by default. (Note that this is a registry setting. Also, remove dead references to HiDPI flag.). This patch is based on portions of girard's patch here https://codereview.chromium.org/232483005/

BUG= 149881 ,  362245 

Review URL: https://codereview.chromium.org/294293002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@273211 0039d316-1c4b-4281-b951-d872f2087c98


Referencing hard-coded Google registry keys like "HKEY_CURRENT_USER\SOFTWARE\\Google\\Chrome\\Profile" outside of /chrome isn't great for Content API applications that are not Google Chrome. I think the hidpi value should instead be set programmatically via a gfx function. Code in /chrome can refer to the Google registry key when setting the value while other Content API consumers can use their own preferred approaches.

Comment 198 by cpu@chromium.org, May 30 2014

marshall,

The decision to opt in to hidpi awareness needs to be done very early, we tried later at the chrome layer and it was too late; it was originally in about:flags using their framework.

I guess we could take a patch that allows you to use \\Company\\Product\\ in the middle  path of the key.
If it's on by default now, is the registry key even needed anymore? (assuming the registry key is used to tell the code to enable hidpi)
@comment#198: It appears that the first call to gfx::IsHighDPIEnabled() comes via ResourceBundle and ChromeMainDelegate::PreSandboxStartup(). Couldn't ChromeMainDelegate call something like gfx::SetHighDPIEnabled(ReadRegistryValue(...) == 1) before initializing the ResourceBundle?
Hi

Has a new release of Chrome introduced a regression here? I was happily using high DPI (only required ticking the box in the properties of the shortcut). Then suddenly tonight, Chrome upgraded and I'm now stuck with a really large resolution :(

Screenshot attached.

Is this a regression? It's really blurry and very annoying! How can I can force Chrome to use high DPI settings again? 

(note: I've tried uninstalling Chrome/changing dev channel, tried the registry fix, installed Canary, all have the same issue).

example1-ie-vs-chrome.png
1.3 MB View Download
#201, what is your display scale set to? It seems like you actually want low dpi settings on a hidpi display? (i.e. really small text?)

The blurriness is being worked on at  issue 370074 .

You can force back to a 1.0 scale with --force-device-scale-factor=1 on the command line if you're comfortable doing that.
#202: He means that pages aren't rendered at 1:1 pixels. This is a common misconception among Windows users.

#201: Under Settings, click Show Advanced at the bottom, and look for Page Zoom. Actually, the setting you want is 80% but it isn't in the list! This is kind of funny since Firefox has the opposite problem and is missing 67% from their list... Wow.
Thanks - the --force-device-scale-factor=1 did the trick. Not sure what the setting was before - how would I find out?
#201, this bug has been reported at  issue 380317 . 
Since enabling the hdpi reg file I have noticed that Chrome is failing to render gmail and constantly the page just goes white. This is also an issue with Trello when constructing long notes. 

Any suggestions?
RE: #199 asvitkine@chromium.org
The registry key can also be used to disable high dpi (setting the value of HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\Profile\high-dpi-support to "0"), so yes, it is probably still needed.
@inverse - the Gmail issue has been reported and is now being tracked. It's here: https://code.google.com/p/chromium/issues/detail?id=380732

highdpi support doesn't work properly across multiple monitors in Windows 8.1. Everything's fuzzy when moving a chrome window to an external (regular DPI) monitor.
I don't think the 8.1 multimon mixed dpi support is in scope for the first attempt at shipping hidpi. We should log a separate bug for that.
The suggested fix now no longer works. I've had to move to scale 0.8, but even that has problems (the menus, buttons are all scaled as well and there are some black areas that now appear on screens, for example on this site when opening the dropdown for searching issues).

Any ideas what's going on?
See screenshot for an example!
-scale.png
206 KB View Download

Comment 213 by Deleted ...@, Jun 18 2014

I updated registry and got the picture right, but now as people have mentioned, I can't drag the window or the tabs.  A real fix would be nice right about now.

Comment 214 by men...@gmail.com, Jun 23 2014

What has happened with this bug?
It used to render OK, but today I opened (beta channel v 36.0.1985.84 beta-m) Chrome - and everything is horribly pixelated again (I run Windows at DPI scale factor 200%).

I went to check HKEY_CURRENT_USER\Software\Google\Chrome\Profile\high-dpi-support - it was set to 2.
It was surprising, since I set it to 1 some time ago, but OK. I closed Chome, changed it to 1, relaunched Chrome.
Everything is pixelated again and the registry values has been changed to 2.
Why Chrome overrides the value, and why it dropped support for high DPI?
Is there any way to disable this setting?

I am unable to use Gmail, Trello, Duolingo with Chrome now thanks to the inability to disable this on  '37.0.2054.3 m' by either removing the Profile registry key or setting this to 0 or 1.
Updated to the DEV channel according to the suggestion in this bug:

https://code.google.com/p/chromium/issues/detail?id=380732#c19

And now I am able to once again use this web apps!

Comment 217 by mabi...@gmail.com, Jul 22 2014

On the latest stable build 36.0.1985.125 and confirming the high-dpi-support registry setting is no longer working. Every time I launch Chrome this setting is getting set back to a "2". It appears that there is a fix in the dev branch, but is there another work around? I would prefer to keep on the stable branch.

Comment 218 by cpu@chromium.org, Aug 15 2014

Labels: -Iteration-73 -Iteration-76 -Iteration-77 -Iteration-78 -M-30 M-37
Owner: cpu@chromium.org
Status: Fixed
HiDPI support is locked for M37. That is, is in good enough shape that we will ship it.

If you are using chrome beta channel and still have issues please chime in on this bug or in  bug 160457 .


Comment 219 by jay...@gmail.com, Aug 15 2014

Thanks for the update, chrome beta works fine on my external monitor, but still blurry on laptop monitor. Both monitors are HiDPI, but laptop monitor has higher DPI than external monitor.
I'm running Windows 8.1 x64.

chrome37.png
853 KB View Download
Graphics upscaling is pretty horrible looking on Windows with a 200% setting...  Eg: http://finviz.com/futures_charts.ashx?t=ALL&p=d1
Maybe you fixed some things, but you broke others.

I increased my DPI to 125% so that Windows icons could be bigger as they are normally tiny on my 1920x1080 21 inch screen. In Firefox, this had the side-effect of scaling pixels up. Now it's the same for Chrome. At 100% screen size, a pixel should be a pixel, not 1.25 pixels!
(At least we should have the option to disable this without using the command line -- which I am not sure is working in the Dev build.)
Chrome displays super small text by default on my new PC. It's getting annoying enough that I'm ready to switch browsers. Please fix this problem!
I've switched to Firefox until this is fixed.

Comment 225 by Deleted ...@, Mar 20 2015

This doesn't seem to be fixed. I'm running Windows at 150%, and still have to run Chrome at 150% page zoom so that content is the proper size (which makes all the content blurry, and still leaves the Chrome chrome very tiny).

Very frustrating to have to choose between tiny content, blurry content, or just giving up and using IE.
Agreed - this does not seem to be fixed despite the resolution - can reopen it please?

Using 150% scaling on 2 Dell P2415Q on Win 8.1
Chrome - Version 41.0.2272.101 m

I can have sharp text if I set chrome flags to force DPI scaling (factor 1.0) and set windows compatability to disable scaling and then zoom in chrome to 150% - but then I have small icons and issues with menus etc.

If I remove all startup flags and compatability tweaks then the text in the browser is blury
Note: I was using "Let me choose one scaling level for all my displays" (as they are all the same.  If I disable this and then set each display to use the same scaling level then the text is crisp and everything works as expected.

Comment 228 by Deleted ...@, Mar 24 2015

Update to my previous comment: Chrome at 150% *does* appear to scale properly after rebooting Windows with the external display already plugged in (I initially got the blurry issue when plugging in an external display while Windows had already been running)
Why this marked as fixed? Chrome is the last browser which fails to work properly on my laptop. Win8.1x64. Firefox was fixed ages ago, IE too, even opera which is based on chromium works fine, but chrome itself still looks horrible.

Comment 230 by Deleted ...@, Apr 24 2015

Huh. It seems to be kind of working but the resolution used for the UI elements like tabs and the navigation bar seems to be hard coded to 196dpi. At least it seems to always be the same size regardless of what I set the DPI of the screen to. If I set it to 1440 using xrandr I get comically large fonts in the menus and tab titles but the size of the elements doesn't change. And if I set it to 144 which is my preferred setting I get smaller fonts but the tabs stay the comically large self.

I've resorted to doing:
$ xrandr --dpi 144
$ google-chrome-beta --disable-gpu --force-device-scale-factor=1.5 &

But Chrome should really get the device scale factor from the screen geometry in xrandr, no? Is it getting it somewhere else I should adjust?
Chrome on my Windows 10 machine will adjust to Windows 10 DPI setting of 150%... however, it does not adjust to Windows 10 DPI setting of 125%, which is the optimal setting that makes everything look good on my 1920x1080 15" laptop display.
#231 I can confirm this too.
I also confirm it.
Still not working for me at 125%:

Windows 10
1920x1080

See attached comparison between firefox and chrome.
highdpi-chrome-bug.PNG
400 KB View Download
Still having an issue where I have two different DPI monitors (Laptop 4k, 27" 4k) under Windows 10. Clicking through extension menus has an offset on the mouse.
Showing comments 137 - 236 of 236 Older

Sign in to add a comment