(No comment was entered for this change.)

(No comment was entered for this change.)

sail, cpu: we don't do any hidpi stuff on windows, so this is expected for now, right?

I'm guessing this is expected for now, but I added this bug/issue to say using Chrome on a hidpi display on windows kinda blows. I currently cant use Chrome because of it and am being forces to use IE10 (which I really would prefer not to have to do). The Chrome team was able to mobilize fairly quickly for the Mac side of things and I'm really hoping that any work there can be used to make improvements here.

Yep, lack of high-DPI support on Windows is a known issue (there aren't a lot of devices so it hasn't been a high priority so far). I don't see an existing bug though (gideon?)

What scale factor does Windows 8 choose to use in this configuration (in both Metro and Desktop mode)?  Our big problem with high-DPI support for Windows is that Windows prefers non-integer scales like 1.4x and 1.8x, where all the work we've done for MacOS is 2x.  See http://blogs.msdn.com/b/b8/archive/2012/03/21/scaling-to-different-screens.aspx for some details.

There wasn't an existing bug - thanks for filing this. I'm currently working on finding an owner.

If it helps, by default, it goes to 150% DPI. With this setting, metro apps, visual studio and IE are all great. But some of the older system dialogs and programs like Skype/Chrome are fuzzy. 

I know that this isn't a priority and I can understand why, and I know it was my choice to get a HiDPI screen, but I don't think I can keep using Chrome until its fixed. IE just looks so sharp in comparison and the HiDPI screen screen makes reading so much easier.

I really hope that this issue can get some love sooner rather than later as I really love using Chrome.

The "fuzzy fonts" is usually because Windows is using display scaling.  This seems to be based on a ruleset from Microsoft, but can be overridden by a user by right clicking the shortcut to Chrome, and under the Compatibility tab, setting the "Disable display scaling on high DPI settings" checkbox (see attachment).
That being said, the latest Windows Update seems to have changed the ruleset for me, and so the fuzzy font issue may go away.

With scaling disabled, fonts in Chrome look great, but the Chrome UI elements (tabs, omnibox, scrollbar) become tiny... (the tab in the second screenshot is not even the width of my thumb) 

An option to enable the 2x option for these elements would be great as a short term fix, as it would be perfect for those people running Windows on a retina MacBookPro, and those on non-integer scales in between could choose...

	Chrome-Compat.png 83.0 KB   View   Download

	Chrome-NonFuzzy.png 113 KB   View   Download

I've tried this solution and it "works". That said its not ideal as the shell is very small and to see anything on the page you need zoom in. Unfortunately the conscience of doing this is a drop in performance and some pages layouts are a wonky. 

 Issue 152447  has been merged into this issue.

I should add that another aspect to be considered is the notifications popup dimensions - presumably the title bar in the attachment would be resolved by the same global shell scale factor, but would the dimensions use the scale factor as well? 

Otherwise, a refinement might be that the zoom setting should adjust the container size along with the content...

	Chrome-Notifications.png 38.8 KB   View   Download

Just wondering if there has been any updates to this one?

While this issue is most apparent for those with Retina displays, it's also a usability issue in general.  There are plenty of people out there with poor eyesight that use HiDPI scaling.

(No comment was entered for this change.)

Gene will hopefully be fixing this up in the next few days, or at least ascertaining what needs to be done.

Huge thanks for the update!!! Really excited about getting this fixed.

(No comment was entered for this change.)

When setting the Window display zoom factor click on Custom Sizing Options, then select "Use Windows XP style scaling". Then set the zoom factor in Chrome to suit.

"Windows XP style scaling" is not a solution to this problem.  It's a system-level workaround that degrades the behavior of the whole OS.

A much better workaround for Chrome's missing scaling support is to use the "Disable display scaling on high DPI settings" compatibility setting to enable that workaround for just Chrome.

(No comment was entered for this change.)

I have the exact same issue. Pleaaasee fix this. This lack of scaling at high resolution displays has been an issue since 2009 in Chrome, yet it is not fixed.

we are discussing the possibility of pkotwicz@ working on this for M26. (Peter, would that be amenable to you?)

hmm, I'm using the word 'amenable' incorrectly. but you know what I mean.

Not knowing exactly what chromium time frames are, but from now, how far do you estimate that being out and is M26 the same thing as v26?

M26 = v26, yes.

We don't pre-announce release dates, but in general we ship a new Stable version of Chrome every six weeks (modulo holidays and whatnot): http://blog.chromium.org/2010/07/release-early-release-often.html

and M23 Stable was released in early November: http://chrome.blogspot.com/2012/11/longer-battery-life-and-easier-website.html

I'll let y'all do the math :)

Originally this was M24 Priority 1, then M25P1, then M25P2, now... M26P2?  Is it going to stop there?

I'm sorry it's been such a frustrating issue for you! We're prioritizing this among all the many things we need to work on for Chrome on Win8, and there aren't a lot of high-DPI screens out there right now. That said, yes, we're serious this time :).

(No comment was entered for this change.)

based on email thread, kevers@ will be helping w/ this (thanks)

By the way, this isn't just a Win8 thing, it's a Windows thing in general.

 Issue 115039  is dealing with the same problem, and it says 'WONT FIX'.

Retitled.  Our approach will be to enable high dpi across win/chrome. This bug will track the high level enabling, and the enabling of the contents frame.
Was: Windows 8 in high-DPI has fuzzy fonts

(No comment was entered for this change.)

 Issue 150876  has been merged into this issue.

I'd just like to add my use case - using a PC on an HDTV I set the scaling in Windows 7 to 150% as I'm sitting far enough away from the TV to not be able to read the screen at regular size.

Chrome's fonts are noticeably soft in this setting, given Chrome already supports arbitrary content scaling wouldn't it be relatively simple to change the render mode of the window to handle scaling manually in Chrome instead of relying on Windows to interpolate the window size up?

FYI, I have the exact same use case as brainfla... and here's my workaround:

1. Right-click the shortcut/icon you use to launch Chrome, select "Properties". In the "Compatibility" tab, check "Disable display scaling on high DPI settings". Click "OK".
2. Launch Google Chrome, open the "Settings" tab. Click "Show advanced settings..." at the bottom of the page and under the "Web Content" heading, change "Page zoom" to "150%" (or whatever you want the default zoom to be). Close and reopen Chrome and you should be all set. The controls will be small but the content will be nicely scaled (text sharply upscaled), which is really what matters.

I also have exactly the same use case as brainfla and viettam. Using Win8 on my htpc, display is an HDTV. I also use the workaround identified by viettam, but in my case I DO mind that the controls are too small.

Chrome scales with Windows DPI at 150%, but having 6 or more tabs open will cause the rightmost tab to overlap the minimize, restore, and close buttons on my 1920x1080 screen. When Windows DPI is set to 125%, Chrome looks as though the DPI is at 100%.

So when can we expect an update with DPI scaling? I feel that the introduction of high-res displays shouldn't be the reason it's just now being developed.

It seems abundantly clear that the future is going to bring us a wide variety of displays of various sizes and resolutions. I hope that the planned solution here is not to support the simple, obvious ratios of common hardware like 2x or 1.5x. 

A future-proof, multi-platform UI should be designed to work at any resolution. For something as fundamental as a browser, you may want additional controls that allow the user to override the OS-level settings. I don't really think Chrome's current "set default zoom" is quite what you want here, because of the way it interacts with the "actual size" setting and because it doesn't affect any of the other UI elements.

Keep up the good work here: I'm excited to see Chrome properly handle a variety of displays. It already looks good on my Retina. :-)

(No comment was entered for this change.)

I am among the victims affected by this issue...

I see a label listed in comment #44, does this mean that this issue has been fixed and updated in source control?  If so, do we know when it will be released?  Thanks!

Hi Dan - The label simply means that we're currently working on it.  

We don't (generally) announce when a feature will be delivered until we've actually coded/tested/verified it.  If you want to stay informed of our progress, watch this issue (you can use the "star" to get on the update list.) (Check for the status  switching to "fixed".)

I can't believe so many people use Google Chrome and call it a high quality browser when it can't even do simple stuff like high DPI scaling properly.

Firefox has been able to do this for YEARS: disable Windows DPI scaling, open Firefox, about:config page, search for layout.css.devPixelsPerPx and then adjust it to a value which corresponds to the amount of zoom in Windows 7.  In my case, as my "scale to this percentage of normal size" value is 150%, I set layout.css.devPixelsPerPx to 1.5.  Bam.  UI and webpages are all increased in size, with text still looking sharp and page elements across 95% of websites looking as they should (for the 5% that don't, it's probably not a website you're going to visit more than once anyway).

Firefox also has a better range of ad blockers, and Tab Mix Plus which makes it incredibly powerful, to the point where it being a bit slower/worse with it's Flash support than Chrome is entirely forgivable.

So yeah... that this simple usability issue still exists and hasn't been fixed does not speak highly of Chrome, really.  Especially considering how many people work on the codebase (I'm assuming a lot).

bump. i don't want to use internet explorer ;)

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=179899

------------------------------------------------------------------------
r179899 | kevers@chromium.org | 2013-01-31T17:24:42.390513Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/display.h?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_guest.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_guest.h?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_win.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/surface/accelerated_surface_win.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_win.h?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/screen_win.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_impl.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/port/browser/render_widget_host_view_port.h?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/win/dpi.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/app/content_main_runner.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/web_contents/web_contents_impl.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/win/dpi.h?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/layout.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/display.cc?r1=179899&r2=179898&pathrev=179899
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/test_render_view_host.h?r1=179899&r2=179898&pathrev=179899

Fix high-DPI on Windows to make use of DIP scaling in WebKit.

BUG=149881


Review URL: https://chromiumcodereview.appspot.com/11953054
------------------------------------------------------------------------

Thanks for the prompt attention to this problem!  It appears there is a fix to this issue that is now in the trunk?  Is there a date for the next release that will include this change?

The patch in comment 50 is part of a series of patches required to fully address high-DPI on Windows.  We cannot comment about the planned completion date; however, rest assured that we are working to stabilize the feature in a timely manner.

Does this update will display images x1 and x2 by definition when using a resolution 100DPI or 200DPI.

Hi,

Just to let you know that I tried builds from here:
http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?path=Win/179905/
http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?path=Win/180293/
and also I tried Canary Chrome today.

The problem stills exists for all versions.
I tried on Windows 8, Samsung ATIV smartPC 700. DPI 150%.

marchelo: Thanks for your help in this. This bug has not been fixed yet, so I'm not surprised that our latest builds still fail in your tests.  (You can watch the "Status" field, and wait for it to go to "fixed" or "verified".)

rbessem: When this update is complete, chrome will scale with the user's OS setting for scale.  So images in the web page will scale up.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=180431

------------------------------------------------------------------------
r180431 | kevers@chromium.org | 2013-02-04T17:03:13.174825Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/native_theme/native_theme_win.cc?r1=180431&r2=180430&pathrev=180431
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/native_theme/native_theme_win.h?r1=180431&r2=180430&pathrev=180431

Fix painting of scaled themes in Windows in high-DPI mode.

BUG=149881


Review URL: https://chromiumcodereview.appspot.com/12114049
------------------------------------------------------------------------

For all who waiting:
This update also didn't solve the problem.
Tested on: http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?path=Win/180446/

Dev team:
I understand (99%) that you knew that. But other may not knew that.

(No comment was entered for this change.)

Please, fix this issue as faster as possible - it is really annoying...

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

Just a comment: there's going to be a lot of affected users with the 208dpi Surface Pro starting to take off. Any word on progress for this particular issue?

since having this blurry chrome thingi going on, i just realized how important this browser has become. give us hope, how far to a solution are you ? 50% ? 95 %? :)

Would love a progress report en this too! - my entire team is hit by this issue. 

i have a surface pro and also would love this to get fixed asap, chrome really sucks on surface right now, its too damn small, or too damn fuzzy.

i have a surface pro and also would love this to get fixed asap, chrome really sucks on surface right now, its too damn small, or too damn fuzzy.

Hi folks - We're working hard on this one and making good progress, but at this point I can't predict how many more issues we'll have to fix to get this working.... 

I appreciate that this one is causing grief, and I feel your pain - I'm running in highdpi mode all the time now, so I'm seeing this bug every time I look at chrome. I'd love to get this one fixed.

Thanks for the feedback. Good to hear there is progress. Think the most important thing is just knowing its not forgotten. 

And thanks for all the good work! We love this browser!

If I'm not mistaken, he also works on mode Metro.. It is always good to have news about it.

great news

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=186170

------------------------------------------------------------------------
r186170 | kevers@chromium.org | 2013-03-05T13:31:06.588327Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/display.cc?r1=186170&r2=186169&pathrev=186170
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/screen_win.cc?r1=186170&r2=186169&pathrev=186170

Set the scale factor for the display on Windows when in high-DPI mode.

BUG=149881


Review URL: https://chromiumcodereview.appspot.com/12398019
------------------------------------------------------------------------

Will fixing this issue of DPI scaling also fix the whole "touch is horrendous on the Surface Pro" issue?  I can't believe how bad touch scrolling is compared to IE10, it only works in the upper left quadrant and often ends up highlighting text randomly to boot.

Otherwise, thanks for working on this!

#73: "Will fixing this issue also fix touch on Surface Pro?"
A: Yes, it will. Making chrome DPI-Aware will correct the touch bugs we are currently seeing on high dpi devices like the surface. 

In addition, we have a fix for touch on high dpi devices - see  issue 175542  for details.

(No comment was entered for this change.)

(No comment was entered for this change.)

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=188432

------------------------------------------------------------------------
r188432 | girard@chromium.org | 2013-03-15T17:24:22.493653Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/win/dpi.h?r1=188432&r2=188431&pathrev=188432
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_desktop_root_window_host_win.cc?r1=188432&r2=188431&pathrev=188432
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/glass_browser_frame_view.cc?r1=188432&r2=188431&pathrev=188432
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_frame_win.cc?r1=188432&r2=188431&pathrev=188432
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/win/dpi.cc?r1=188432&r2=188431&pathrev=188432

Correct title bar size for HiDPI Windows

GetSystemMetrics was reporting title bar height in pixels, but we were interpreting them as DIP. This resulted in a double-scaled title bar. 

BUG=149881

Review URL: https://chromiumcodereview.appspot.com/12684006
------------------------------------------------------------------------

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

So what started off as M-24 is now M-28.... disappointing.  

I also am disappointed by this. When Retina came out support for hidpi came pretty soon, but on windows we had the high-end laptops with full hd resolution and small screens for a few years now and no support. 

I had to switch back to IE10. But now that I am using IE for a while, I am amazed to see how far IE has come. I actually don't miss Chrome that much. I miss the resume tabs feature of chrome, but can live without it

------------------------------------------------------------------------
r192750 | kevers@chromium.org | 2013-04-06T15:55:07.562181Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/views/widget/desktop_aura/desktop_screen_position_client.cc?r1=192750&r2=192749&pathrev=192750
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/views/widget/desktop_aura/desktop_root_window_host_win.cc?r1=192750&r2=192749&pathrev=192750

Fix window positioning in high-DPI on Windows.

BUG=149881

Review URL: https://chromiumcodereview.appspot.com/12512014
------------------------------------------------------------------------

kevers@, I realise this isn't done yet, but am I correct to assume that none of the changes committed so far have any effect on normal builds at all due to the lack of the Chrome manifest declaring that it's high-DPI aware? If so, is there any way someone can test this without doing their own build?

Also, should we update the title of this bug? Win7 and Vista also have this problem/feature, it's not Win8-specific.

 Issue 142874  has been merged into this issue.

torne@,

High-DPI support is currently behind a compile time flag, and not testable without a custom build.  There is more behind the flag than a manifest declaration. Gladly post a comment once the feature is testable.

Though a portion of the high-DPI work is Win8 specific, you are correct in that the bulk of the work also applies to Win7 and Vista.  Updated the title.

I have noticed using Flash Player in Full screen that even with DPI in Windows 7 set at 96DPI I get varying Full screen resolutions especially noticed when using Flash player to play Amazon instant video. Sometimes its OK sometimes it lowers the resolution and makes everything appear fuzzy as if it has gone out of default resolution for the screen. In my opinion its one of the worst issues as I have tried to set DPI to 125% on my laptop for eyesight reasons and everything works well except for Chrome.
Maybe this is another reason Google is forking Chrome away from WebKit? 

 Issue 175003  has been merged into this issue.

With the Toshiba Kirabook just having gotten released (I'm typing this on one), there's now a retina grade display on a windows computer. I know you're hard at work on this and appreciate the work you do. Just thought it should be worth considering when prioritizing against other issues. Thanks.

Moving all non essential bugs to the next Milestone.

PLEEEEAAAAASSSSEE hurry up and fix this! Surely it doesn't need to take this long to fix what seems a simple issue...one that makes Chrome UNUSABLE FOR MANY OF US! 

I agree with other comments too this is not just related to a small number of devices. I use windows 7 at home and at work and it is a problem for me on both.

Also with text scaling on several other things are broken in chrome as well the window resizes itself into the taskbar when maximized, the new tab button and parts of the rightmost tab/tabs display over the min/max/close buttons.  Fullscreen flash player ie play a youtube video and click the fullscreen button leaves a black bar at the bottom of the screen all of this in windows 7/8 connected to a tv and on a Microsoft surface pro tablet.

Bump. I use Windows on the Retina MacBook Pro so this is kind of a big issue for me. Well, not for me since this bug forced me to use Firefox. Which, by the way, they're enabling high DPI support in version 22* so you may not want to fall further behind.

*Previously a tweak would enable it.

Please don't post saying "this is important, please fix" - we know and people are working on it. It just causes unnecessary email to be sent to the ~140 people who are following this bug.

My apologies. I'll avoid trying to interact with Google in the future.

Pardon our impatience. If this issue affects you, it affects you in a bad way making Chrome hard to use and much worse than the other browsers. Plus you promised a fix "in the next few days" last November.

And you fixed it so fast on Mac.

stevens, edwardsgreg: That wasn't what torne was suggesting. If you want to show your support and interest in a bug, you can "star" it (like 137 other people already have!). Adding a "me too" message on the bug causes spam/makes the bug harder to read/doesn't actually help get the bug fixed... 

(With apologies to everyone that just received spam from me)

(No comment was entered for this change.)

(No comment was entered for this change.)

Will this be marked a dupe of issue 679 (which has been open since 2008.09.03), or vice versa?

No fixes for this yet? Major fail Google :(

------------------------------------------------------------------------
r205831 | girard@chromium.org | 2013-06-12T17:00:14.245690Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/tabs/dragged_tab_view.cc?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/win/dpi.cc?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/win/dpi.h?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/views/widget/native_widget_win.cc?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/thumbnails/simple_thumbnail_crop.cc?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/win/events_win.cc?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/canvas_paint_win.h?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/views/widget/aero_tooltip_manager.cc?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/views/win/hwnd_message_handler.cc?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/views/win/hwnd_message_handler.h?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/views/controls/native/native_view_host_win.cc?r1=205831&r2=205830&pathrev=205831
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/views/widget/tooltip_manager_win.cc?r1=205831&r2=205830&pathrev=205831

Enable high dpi in win/views.

BUG=149881

Review URL: https://chromiumcodereview.appspot.com/16336027
------------------------------------------------------------------------

I tested the latest dev Chrome and problems of tab is now resolved. Good work..

------------------------------------------------------------------------
r208331 | girard@chromium.org | 2013-06-25T00:56:12.153913Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/canvas_paint_win.h?r1=208331&r2=208330&pathrev=208331

Rounding error in HiDPI canvas.

Rounding is not appropriate if the scaling factor is not an integer.
(And if it is an integer, it's not necessary.)

BUG=149881

Review URL: https://chromiumcodereview.appspot.com/17505003
------------------------------------------------------------------------

This has been implemented in Firefox 22.
Is this feature close to being implemented in Chrome?

looking forward to this improvment - any progress on this issue?

RE: #110, #109, #105, and quite a few more...: Yes, there has been a good deal of progress on this issue. If you want to try it out, run the current canary build, and add the flag --high-dpi-support=1. 

Note that there are some issues with fonts - these will be dealt with as part of  issue 249099 . Any other issues should be reported (not here though!!! open new issues please.)

 Issue 139975  has been merged into this issue.

 Issue 121365  has been merged into this issue.

 Issue 94594  has been merged into this issue.

 Issue 123701  has been merged into this issue.

Just FYI, this got some press yesterday :)
http://news.cnet.com/8301-1023_3-57593030-93/chrome-gets-high-resolution-screen-support-on-windows-too/

Keep up the good work!

Google you so lame. On a high res display (1600x900 14 inch), Windows 7, I have to set DPI scaling to 150%. Firefox works perfectly and displays crispy text. Chrome so lame. I have to disable DPI scaling, which makes text in Chrome so tiny they hurt my eyes.

ok i tried the cleartype thing in win 7  and the dpi thing in chrome and doesnt work!!
firefox an ie works fine ...3 my eyes hurt!! 

	chrome isssue.jpg 287 KB   View   Download

I tried the Google Chrome 30 beta on a high-dpi screen and it still looks blurry. Is the fix supposed to be turned on in 30?

RE: #119 - No, it is not enabled by default. There are a number of outstanding issues that still need to be addressed - these are detailed in  issue 160457 

Now it can be enabled via chrome://flags and it works, but contains a lot of bugs. I hope it will be fixed soon.

This problem still remains I am using the new Yoga 2 pro and have HiDpi enabled and the fonts and everything else is very blurry on chrome, compare it to IE11 and it is a disaster i even think it is unusable.  

I know that everyone will be notified and that I shall not post a "me too" comment... but "me too" ! I am very sorry to say it like this but it's been a year now Google, WTF really ?

How comes the Mac users and there tiny market share get an update in no time, even though it's a bit more difficult to go from 96dpi to 150dpi instead of x2 everything ?

There is a lot of high dpi devices out there now, not only the nerds installing Windows on their Retina Macbooks.

I can confirm that on 33m-dev the launch flag works. I still had to adjust font-sizes for Windows to get the menus and tabs correct (and I had to relaunch Chrome to get the tabs changed) but there are still a few scaling issues left with buttons such as the menu button, navigation arrows, refresh, home, and the expand button for the chrome extensions (to the right of the address bar). It's a fairly minor issue for those who don't use those buttons much which I imagine is most users that it would affect, but it looks to be the only bit left that really keeps Windows and high-dpi (200% on the MBP Retina 15" in my case) from looking great.

Yoga 2 PRO user here as well. Chrome tabs are pixelated and fonts are looking... well bad - too light. Running stable 31 (first time commenting here, cause this issue is a blocker for me to use Chrome). Even the Chrome icon is pixelated.

The HiDPI flag was working in 33, but stopped working after Canary updated to 34.

When I enable the HiDPI support on my new XPS 15 9530 (Win 8.1, 3200x1800, 15") and then restart Chrome I cant use it anymore nor uninstall it, because there are no buttons visible anymore and I cant click anything anymore. I always have to remove everything manually and then stop reenabling the hidpi support again.
I've tested it under Chrome 31, 32 and 33.
After the restart I see the content of the screenshot but can't click anything.

	chromebug.PNG 104 KB   View   Download

I have the same issue as #128. Chrome becomes totally unusable when I enable the HiDPI flag and restart.
I am using a Lenovo Yoga 2 Pro at 3200x1800

Having Yoga 2 Pro too. Have to delete my chrome appdata files to make Chrome usable. 

Had to chime in. Just started up my new Yoga 2 Pro at 3200x1800 for the first time, and first thing I did was download Chrome. Blurry, terrible text. Both IE10 and Firefox text are just fine. I refuse to disable DPI scaling in Chrome properties, because that makes all the UI control so freaking small it's unusable. Come on, people. There's been enough time to fix the text. Someone update this PLEASE...Don't make me use IE10...please.

Lots of people turning on their Yoga 2 Pros, like me right now.  Google, what's the hold up?

I just wanted to add another Yoga 2 Pro voice to the thread.  There are numerous ultra-HD and quad-HD notebooks out now, and consumer-friendly 4k desktop monitors on the horizon.  I hope this issue gets resolved soon!

I have a Macbook Pro Retina running Windows 8.1 on Bootcamp. Chrome is incredibly blurry/pixelated on default settings, has weird font problems and messed-up UI elements with the High DPI flag on, and the whole UI is unusably tiny if I turn off scaling. Currently I am using Firefox, but I really hope this is fixed soon since I really like Chrome in every other way, and use it on all my other devices. Every other major browser works fine with High-DPI, so why can't Chrome?

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

The second bad news is that the hidpi flag you see in chrome://flags sometimes does not work, we are trying to figure out in what cases but is definitely more prevalent in win8.1 than on win8. We are trying to find what is the root cause.

The good news is chrome 34 (canary) hidpi support is way better, but you have to opt-in by editing the shortcut that you use to start chrome. The chrome://flags way is still broken.

So for canary find the shortcut and edit it, adding --high-dpi-support=1, close it and restart chrome, verify that the flag is being applied by going to chrome://version , you should see the flag there. Text should be crisp and the UI elements too.

girard@ I re-opened the bug. Please close it when the issues above are worked out.

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.15.36 AM.png 9.0 KB   View   Download

	Image 2014-01-14 at 8.16.48 AM.png 3.5 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.

Thanks for trying, we are tracking

PDF viewer:
https://code.google.com/p/chromium/issues/detail?id=333291

Download icons:
https://code.google.com/p/chromium/issues/detail?id=334336

Silverlight wrong size:
https://code.google.com/p/chromium/issues/detail?id=334343

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".

> 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.

(No comment was entered for this change.)

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? :/

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

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?!

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

------------------------------------------------------------------------
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.

(No comment was entered for this change.)

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 :)

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)

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!

RE #178: Font spacing will be fixed as part of  issue 25541 

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.

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

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.

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?

------------------------------------------------------------------
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.

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.

------------------------------------------------------------------
r273211 | ananta@chromium.org | 2014-05-28T13:59:45.531486Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/gpu/gpu_process_host.cc?r1=273211&r2=273210&pathrev=273211
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/chrome_browser_main_win.cc?r1=273211&r2=273210&pathrev=273211
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/plugin_process_host.cc?r1=273211&r2=273210&pathrev=273211
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/switches.cc?r1=273211&r2=273210&pathrev=273211
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/win/dpi.cc?r1=273211&r2=273210&pathrev=273211
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/switches.h?r1=273211&r2=273210&pathrev=273211

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
-----------------------------------------------------------------

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.

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

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.

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!

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.

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 .

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.