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

Issue 160457 link

Starred by 158 users

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

Windows HighDPI support in desktop mode

Project Member Reported by thakis@chromium.org, Nov 11 2012

Issue description

This is a tracking bug for highdpi support in desktop chrome. (From what I understand, metro mode mostly works already?)
 
Showing comments 29 - 128 of 128 Older

Comment 29 Deleted

Comment 30 by rbes...@gmail.com, Nov 14 2013

I have a feeling that Chrome is a gas works... In addition, the topic was a year between time Windows 8 and 8.1 are out.
So if you do not want to go wasting time to wait for the magical update of Chrome : you have the choice between IE 11 and Firefox support HiDPI (Ratio: 2).
Cc: wiltzius@chromium.org
wiltzius: I wonder if comment 28 is more fallback from winaura.
With v31 HiDPI was broken, but at least mostly functioned. Extension pop-up menus were completely unusable, but the rest of the browser worked. In v32 now it's completely unusable. You get a small square in the top-left corner where part of the screen appears, but it doesn't line up with ANY click or touch events. Meanwhile if you switch to Metro mode you get pretty much the same, with absolutely no hope of ever getting out.

FYI: to those stuck on the desktop mode, you don't need to kill your profile. Just open the LocalState file, search for "DPI" and delete the appropriate flag entry to undo the change.

This seriously needs to be fixed. Chrome on Windows 8.1 on a high-DPI screen is a mess no matter what. 
Labels: -M-33 -MovedFrom-32 M-32
Hi folks. There is a patch in the works to address the regression. I'm still hoping to roll it into M32.
Any potential progress on making extension dropdown menus usable in ANY Hi-DPI mode? Currently in the stable channel they're a no-go, which is a carryover from the v31 beta.

Comment 35 by men...@gmail.com, Nov 14 2013

I've also opened https://code.google.com/p/chromium/issues/detail?id=319195 for new HiDPI regression in STABLE branch (which I installed after realizing Beta is totally broken). Maybe people here might know something about it?

For now, both Stable and Beta are no go, and IE 11 seems like the only option for me :(
Using Version 31.0.1650.57 m

Should the extension menu issue be turned into a separate bug? I'm on a high resolution screen, making unscaled desktop Chrome almost unusable, but turning on the high DPI support flag to 'enabled' leads to a blank drop down menu in extensions such as Ghostery. 

Probably related, the 'find in page' box also shows up on some random location (overlaying the middle right of the omnibar). Is that also a separate bug?

Hovering over the custom search menu leads to 45deg slanted fonts. 

Given the number of high resolution tablets and laptops coming out, hopefully these issues can be addressed soon.
I addressed that issue in ticket https://code.google.com/p/chromium/issues/detail?id=314251 . I merely brought it up here because it seems tied to the overall uselessness of HiDPI mode.
Labels: -M-32 M-33
Cc: jaisimha@chromium.org pbomm...@chromium.org cpu@chromium.org ananthak@google.com melodychu@chromium.org chrome-test@chromium.org mangalampalli@chromium.org zturner@chromium.org karen@chromium.org ligim...@chromium.org
 Issue 308840  has been merged into this issue.

Comment 40 by e...@figma.com, Nov 18 2013

HighDPI cursor support ( crbug.com/161614 ) is related to this issue as well, but I don't see it in the list of blocked issues. Currently custom cursors are really tiny.

Blockedon: chromium:161614
Oy, is this really pushed back to M33? Chrome is almost unusable on many new, high-resolution Windows computers. This will especially start to pop up when people get gifted new computers for Christmastime (~5wks ... on a 6 week stable release cycle).

Those of us on canary/dev/beta will get it earlier (and as general early adopters do expect hiccups from time to time), but I do think the timing here is just going to be bad news, in no small part because of the upcoming holiday season.

Comment 43 by raina...@gmail.com, Nov 21 2013

I can confirm that on 33.0.1712.2-dev-m 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.

Also, the icon animation on the tab has a strange vertical-striping effect so that the loading animated icon is unrecognizable. There is also bad render of fonts in SELECT menus.
Labels: -Pri-2 Pri-1
With high DPI mode enabled in Chrome desktop the context menu shows up at the wrong position in snapped view, see  Issue 324661 .

Comment 46 by ro...@adobe.com, Dec 17 2013

I've just opened a bug with rendering defects on Windows 8.1 with HiDPI configuration:  http://crbug.com/329143 . I think this is similar to comment #28. I didn't find other logged bugs on this issues.
Project Member

Comment 47 by bugdroid1@chromium.org, Dec 17 2013

Labels: -M-33 MovedFrom-33 M-34
Moving all non essential bugs to the next Milestone.
Cc: scottmg@chromium.org briander...@chromium.org ananta@chromium.org vangelis@chromium.org vmp...@chromium.org
 Issue 329009  has been merged into this issue.
Hi DPI mode fails to open a print dialog -- a blank window opens then closes.
@girard: Can you provide a quick update on this bug?

From the blocking issues, it looks like most of the problems are due to missing/miss-handled assets, but I currently see corruption in Chrome Canary like the attachment in comment #28, which doesn't look like an asset issue. Do you know what's causing that corruption? Do you need any support from the GPU team? Are there any tasks that others can help out with?
This may have been a fluke, my Chrome Stable install (Version 32.0.1700.72) with HiDPI flag on spontaneously went from OK to completely unusable today at 7pm EST after a system restart. The window appeared with partial title bar, sometimes no title bar, touches registered at unexpected locations, unusable. Multiple Chrome relaunches didn't fix it, nor did a system restart with Win 8.1 set to 100% DPI scaling . The page area appeared to be rendered starting 'above the top of my screen'. Switching display resolution or screen orientation didn't fix it either. 

The only way out was to 'blindly' reset all flags, so if anyone else gets stuck: launch Chrome, hit Alt-d, type chrome://flags, hit enter, press tab, hit enter, hit alt-F4, and restart Chrome. 

If I re-enable HiDPI, I end up in the same broken state. No idea what changed between 9am today and 7pm today. This is on a Surface Pro 2.
joesixgig: Were you running chrome on the desktop or in metro/modern mode? Also, are you running 8.0 or 8.1?

Comment 53 by Deleted ...@, Jan 8 2014

on chrome v32 and v33 high dpi seems to be "more broken" than it was before. earlier it was not alligned perfectly but it was usable but now its just displaying everything in window that has 1/4 of screen size and nothing can be clicked (only scrolled if it use previously openned tab. low dpi looks normal (but crappy on gorgous yoga2pro 3200x1800 screen with 200% scalling on windows 8.1). 

any fix for this? is disabling update from v31 only option?
highdpi broken.png
97.6 KB View Download
Re #52, this occurred using desktop chrome on a Win 8.1 system (Surface Pro 2). I shut down my SP2 connected to an external monitor (SP2 display off) running at 100% DPI scaling, Chrome HiDPI flag on. Turning the system back on without external monitor attached (defaulting to 150% DPI scaling) and starting Chrome it showed with the display artifacts as in #53, and no change in DPI scaling could bring it back to working order. The only solution was (and still is) keeping the HiDPI flag off, as in #51.

Comment 55 by mazza...@gmail.com, Jan 10 2014

Re #51 to #54, I just got updated to 32.0.1700.72 (stable) and also running Win 8.1 on a Surface Pro 2. Metro mode is completely unusable by mouse or touch - I cannot click on anything. Bookmarks bar has mouseover effects roughly button height distance to the bottom right. Combinations of HiDPI flag and disabling Windows DPI scaling do not make a difference. Desktop mode is fine.

Comment 56 by piv...@gmail.com, Jan 10 2014

I have a new problem on Chrome 32 Beta: 32.0.1700.68 (Official Build 241430) beta-m

When HiDPI flag is set, opening any PDF with the Chrome PDF Viewer, will cause Chrome to 'Aw Snap'. 

Disabling the Hi-DPI flag will cause PDF's to function correct again. It is a repeatable problem. 
RE #56: I opened issue  Issue 333291  to track this. Thanks for the report.
Got the same behaviour as #53 on the same machine (Lenovo Yoga2Pro, 3200x1800, Win8.1, Windows scaling activated) on all three latest versions of stable/beta/dev channel. It was okay on some earlier versions. Why did it go from okayish to unusable and not the other way around?
I hope this will get a fix soon. I'm even thinking about switching back to IE ;)

Comment 59 Deleted

Project Member

Comment 60 by bugdroid1@chromium.org, Jan 22 2014

------------------------------------------------------------------------
r246441 | girard@chromium.org | 2014-01-22T22:51:10.531361Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/win/dpi.cc?r1=246441&r2=246440&pathrev=246441

Disable calls to SetProcessDPIAware under Win8.1 (Rebase)

Was previously LGTM'ed as https://codereview.chromium.org/137483002/
BUG= 160457 ,  329143 
TBR=ben@chromium.org

Review URL: https://codereview.chromium.org/138443006
------------------------------------------------------------------------
I think I solved this recent problem myself by doing the following:

Right click on a Chrome icon in desktop mode, then right click Properties. (See attachment)
Under Compatibility, try making sure Disable display scaling on high DPI settings is checked.
Relaunch Chrome with hiDPI flag enabled.

Worth a try for others having problems again, as I did.

ScreenHunter_21 Jan. 24 17.21.jpg
76.1 KB View Download
That was reported in another, related thread. Creates more problems. Facebook tabs constantly stop responding, and other performance issues. I had to revert after a few hours.
Project Member

Comment 63 by bugdroid1@chromium.org, Jan 28 2014

Labels: merge-merged-1750
------------------------------------------------------------------------
r247476 | flackr@chromium.org | 2014-01-28T18:46:16.249546Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/ui/gfx/win/dpi.cc?r1=247476&r2=247475&pathrev=247476

Merge 246441 "Disable calls to SetProcessDPIAware under Win8.1 (..."

> Disable calls to SetProcessDPIAware under Win8.1 (Rebase)
> 
> Was previously LGTM'ed as https://codereview.chromium.org/137483002/
> BUG= 160457 ,  329143 
> TBR=ben@chromium.org
> 
> Review URL: https://codereview.chromium.org/138443006

TBR=girard@chromium.org

Review URL: https://codereview.chromium.org/137543010
------------------------------------------------------------------------

Comment 64 by men...@gmail.com, Jan 31 2014

I don't understand - Win 8.1 adds per-monitor DPI settings, into which an app can opt-in by calling SetProcessDpiAwareness (a different function!).

Regarding the system-wide DPI settings (into which an app opts-in by calling SetProcessDPIAware), 8.1 should not be any different from 8.0.

Why disable this call, and only specifically on 8.1?
Now neither of 32, 33 or 34-series builds support HiDPI :(

Comment 65 by Deleted ...@, Feb 3 2014

Same workaround as comment #61, however, kerning is terrible and inconsistent on all fonts.
Google Docs document editing is now broken in HiDPI mode

Comment 67 Deleted

Comment 68 by Deleted ...@, Feb 19 2014

Hello,
DPI scalling is still a mess on Win 8.1:
My setup:
- DELL XPS 15 with 15,6" 3200*1800, 150% scaling, Windows 8.1, latest updates on
- connected another 20+" 1920*1080, 100% scaling

Chrome behavior - HIDPI flag off, win DPI scaling on:
- Blurry on DELL
- crisp and sharp on secondary display

Chrome behavior - HIDPI flag on, win DPI scaling off:
- crisp and sharp on dell (except tab borders, etc, but content is great)
- 150% zoom on secondary, so everything is huge and unusable

Chrome behavior - HIDPI flag off, win DPI scaling off:
- soooo small on DELL
- ok on secondary

How come, Firefox, Internet Explorer and many other apps can scale properly on multi monitor setup, even without some "flags" and chrome can't?

Thanks for solving this...
Issue still exists on some elements with HiDPI flag on, "Disabled Scaling on HiDPI displays", Display Scaling=1.5 (Win8.1)

Notably: Pull-down selection boxes, window tabs.
Also: Text in PDF viewer is blurry

User Agent	Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36
Command Line	"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --no-startup-window --flag-switches-begin --enable-pinch --high-dpi-support=1 --touch-events=enabled --touch-optimized-ui=enabled --flag-switches-end
chrome-pdf-blurred.png
72.4 KB View Download
chrome-blurred.png
67.4 KB View Download

Comment 70 by dxie@chromium.org, Feb 26 2014

Labels: m-35 MovedFrom-34
Moving all non release-blocker bugs to the next Milestone.
Sigh. 'cause it's not like it's important that Chrome works properly on the new line of high-DPI computers that are sweeping across the Ultrabook market.

Comment 72 Deleted

@ 71 --- I feel the same way. It mostly works, and printing finally does, but there are still random problems with extensions (floating Hangouts, missing icons, etc) and general hideousness of borders (go aliasing!)

And let's ignore the utter disaster of <select> elements. If you don't know what it already says, it's hard to tell what it's supposed to say.
Absolutely. Kerning is still randomly off in a lot of places, extensions don't display properly, web apps in special windows look weird and touch points are often misaligned, the buttons for a lot of extensions are missing, and in all of my non-primary profiles the back forward, refresh, and menu buttons are all ultra tiny and nearly impossible to click. Just a FEW of that issues. And that's only as a result of me having manually adjusted the high-dpi settings in flags and the shortcut properties. I shouldn't have to do either.

What I don't understand is how:

a. Firefox got past this early.
b. Chrome went through this with the retina MacBooks and fixed the problem in, what, weeks?

Comment 75 by jay...@gmail.com, Feb 26 2014

@72
The real pain is, you can only adjust Chrome with several settings to make it works well on one screen, HiDPI laptop or normal DPI external monitor, but not both.
Bingo, @75. While 8.1 nicely adjusts its scaling between displays, Chrome can't. So I can get it up to about 90% functional on my 3200x1800 primary display, but on my secondary 1920x1200 everything is a gigantic cartoon.
Here there is a fix: On my nice home laptop, with a gorgeous 2560x1440 screen, I now use Internet Explorer most of the time -when enjoying online content. I miss Chrome, though.

Comment 78 by Deleted ...@, Feb 27 2014

I don't get it. How is this bug a 'non-blocker' for release ? Existing functionality is broken for an entire class of machines.

Comment 79 by cpu@chromium.org, Feb 28 2014

So we are changing the way we draw text to use DirectWrite, this is a big change but I think we can do it in reasonable time. Until that text will have uneven kerning on hidipi machines.

For the PDF the blocker issue is shipping the hi-res UI assets. We are trying to figure out how to do this since Our installer is already past a reasonable size.

But we are committed to fix these issues.

Comment 80 by dxie@chromium.org, Mar 2 2014

Labels: -m-35 -MovedFrom-34

Comment 81 by hl...@aol.com, Mar 3 2014

I surely do miss Chrome in Windows mode, with its excellent resolution and user friendliness...  IE just plain sucks (that's a technical term)!!!

Comment 82 by Deleted ...@, Mar 3 2014

Makes sense! Thanks for the response cpu.

Comment 83 by dxie@chromium.org, Mar 3 2014

Labels: -Pri-1 -M-34 MovedFrom-34 Pri-2 M-35
This issue is Pri-1 but has already been moved once, therefore lowering to Pri-2 and moving to next milesone.
Project Member

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

Comment 86 by kareng@google.com, Apr 7 2014

Labels: -M-35 MovedFrom-35
This issue has already been moved once and is lower than Priority 1,therefore removing mstone.

Comment 87 by Deleted ...@, Apr 9 2014

The problem is still here. 
Windows 8.1 Pro, monitor ASUS VS239HV (IPS), video resolution: 1920 x 1080.
I temporarily solved by applying the tips descripted in  Issue 308840  
#36 koraye...@gmail.com and setting the zoom to 125% in Chrome.
https://code.google.com/p/chromium/issues/detail?id=308840

The Google Chrome version is 34.0.1847.116 m
I think this is worth considering, seeing as (somehow) this is lower than "Priority 1":

1. There are more Windows 8/8.1 computers than the sum total of Apple and Linux computers
2. Most people buy new computers rather than upgrade; therefore, there are probably as many or more new Windows 8/8.1 computers as the sum total of Apple and Linux computers
3. Many, if not most Windows 8/8.1 devices (and definitely all "flagships") are high-DPI.

Therefore, this issue probably affects a similar number of people as *Chrome not launching on OSX at all*. It boggles the mind that months later Chrome is the ONLY major browser to not support this. You might as well stop OSX updates with the number of users you're alienating.

Comment 89 by jsi...@gmail.com, Apr 13 2014

Hey , gir...@chromium.org ... there is no such path in my registry. 

https://dl.dropboxusercontent.com/u/16359949/Untitled.jpg
RE #89: You need to create the folder and the entry. If you're not comfortable editing the registry directly, there is a .reg file at https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/U_K1NHuMLic that will  do it for you.

Comment 91 by jsi...@gmail.com, Apr 14 2014

Awesome thanks!

James
@girard: Can you take a look at https://codereview.chromium.org/231723005/ and see if you think this might have any impact on High DPI?  Root window coordinates were (are) all messed up in Ash.  
Hi, I just upgraded my laptop and can't get Chrome do display properly in Windows 8 mode. Been playing with every Windows and Chrome setting that I can dig up without luck. The behaviour seems sporadic, but Chrome works properly if I disable Windows scaling in Compatibility mode. But then I am unable to read chrome fonts because they are to small. It´s a new Lenovo Yoga 2 Pro. 3000x1800 resolution. Cheers, Hawk. 
problem.png
146 KB View Download
windows.png
63.4 KB View Download

Comment 94 by jolu...@gmail.com, May 10 2014

It is a shame that Chrome does not support HiDPI Devices in Windows 8.1 for months. It looks blurry on many modern devices, for example my Lenovo Yoga 2 Notebook. This affects many people, and Chrome is the last browser with this problem.

I will have to switch to Firefox until this bug is fixed.
If you set the registry flag, the latest dev version runs fine for me in HiDPI Windows 8 mode on my Surface 2 Pro.
I tried out Chrome Canary (36.0.1984.1), and when setting the registry key, the high DPI mode works very well now. However, the kerning in Firefox 29 is still noticeably better (see attached screenshots).  

The picture looks sharpest on Chrome 34, though, but that might be due to other things, it does not look high DPI in any case.
Chrome34.png
97.9 KB View Download
Firefox29.png
101 KB View Download
Chrome36Canary.png
98.0 KB View Download
I'm using 36.0.1976.2 dev-m on a ThinkPad Carbon X1 Touch running at 2560x1440 at 14" and most things are working ok with the registry setting enabled, but the nav buttons and extension icons are all rendered incorrectly.
high-dpi.PNG
618 KB View Download

Comment 98 by cpu@chromium.org, May 12 2014

Ok guys and gals. We are near the end of the journey. Thanks for being patient and awesome.

The last piece is to enable DirectWrite, without it the text renders poorly as seen in #96. So please enable this in about:flags  (it is the 5th or 6th item) and let me know how it feels.

Warning note; it is not going to render identical to FF or IE, we are still feeling our way on the exact tweaks but please let us know how it feels.



Comment 99 by cpu@chromium.org, May 12 2014

jham, what scaling factor are you using? are you scaling the text as well? any setting out of the ordinary I shoud know?   

nav buttons are not looking like that for me in hidpi.

In reply to #98:
Chrome 36.0.1976.2 dev-m looks good on a Dell XPS 15 with the 3200x1800 display at 150%. High dpi support is switched on in the registry, as well as Direct Write rendering in chrome://flags. The OS is Windows 8.1 Update 1. I'm using Chrome is in standard mode, not in Windows 8 mode.

Thank you all, well done!


I have the app set to "Disable display scaling on high DPI settings", not running in any compatibility mode.
Looks like we're 80% there. Running on a QHD+ display at 200% scaling (default), on the dev version, with the registry flag set and DirectWrite enabled, we're looking really good. Everything is sharp and clear, all the icons that weren't showing up before (like in app launcher and on toolbar) are back, and I can drag windows again.

The following issues remain:

* Toolbar icons are all tiny. They clearly did NOT scale along with everything else.
* Google Keep application (which I run as its own separate app) has black borders within the window (example attached)
* Floating Chrome applications, such as the app launcher and Hangouts, which should align with the bottom, hover a quarter-inch or so above the taskbar (example attached)
Screenshot 2014-05-12 11.37.02.png
15.5 KB View Download
Screenshot 2014-05-12 11.40.30.png
778 KB View Download
New issue:

I'm running Offline Gmail as its own app, as well, pinned to my taskbar. When replying to an email (or composing any message), the screen constantly refreshes, with random squares appearing and disappearing all over the screen. It functions, but it's difficult to look at and very difficult to type on.

That alone might send me back to lowering my resolution again.
RE:#98

Looks significantly better, though some fonts still seems to render with odd kerning. EG: This forum. Especially noticeable with the following combinations: ce  Gm  we 

Keep it up! SO MUCH BETTER!!! 

Comment 105 by cpu@chromium.org, May 12 2014

Cc: benwells@chromium.org
benwells, see comment #102 regarding google keep. Do you have a separate bug for that?

The odd refreshing and squares are showing up elsewhere in the main browser, too. Nowhere near as frequently as in the Gmail Offline app, but typically when scrolling within sections of a page (such as the Notifications menu in Facebook), and usually only at first.

Also, it feels like scrolling in general, across the entire browser, is more sluggish.
 Issue 308840  has been merged into this issue.

Comment 108 by cpu@chromium.org, May 29 2014

announcement: hidpi is now enabled by default in canary, registry settings not required anymore. DirectWrite is also enabled by default whenever hidpi is so that applies as well.

Comment 109 by dhw@chromium.org, May 29 2014

Why is everything so much larger in Chrome 37.0.2020.0 ?

See attachment for Chrome 35 and 37 running from the same Win7 computer.

Chrome37Canary_EverythingLarger.png
99 KB View Download
Kerning is still ridiculous, it seems. See "oo" in "Google Chrome" on the page #109.
The kerning requires chrome://flags/#enable-experimental-web-platform-features which I don't think gets defaulted on by the hidpi switch. Maybe it should since I don't think subpixel positioning can be separated out from that flag easily.

Comment 112 by rad...@gmail.com, Jul 16 2014

Is the issue with floating chrome windows (hangouts, notifications, etc) actually on anyone's radar? Been suffering with it for months.
I'm wondering how much of ANY of this is on anyone's radar. It's been quite a while since we've gotten any updates, and none of this has filtered down to stable builds yet.

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

Blockedon: -chromium:161614
Labels: -MovedFrom-33 -MovedFrom-34 -Pri-2 -MovedFrom-35 Pri-1 M-37
Owner: cpu@chromium.org
Status: Fixed
Support for hidpi is ready for chrome 37. Which is currently in Beta. 

The text issues are addressed by the switch to DirectWrite + harfbuzz.

I believe it is good enough for shipping. The renaming issues we want to fix in the release after are:

custom cursors:
https://code.google.com/p/chromium/issues/detail?id=161614
sometimes blurry on initial load:
https://code.google.com/p/chromium/issues/detail?id=388908

If you see other issues in Beta please add them to this bug.

Comment 115 Deleted

Both issues from comment #102 are still present. Black borders around all contents of Keep windows, and App Launcher and Hangouts app hover about a half-inch above the taskbar.
I don't see any the black borders on canary @ 1.5x. I don't have 37 handy though, maybe only there?

The app launcher does seem to be strangely positioned. Not sure what the design is, it seems to be bottom-left-ish, independent of where the taskbar and taskbar icon are. I don't think that one is a blocker but we should file a separate bug for that.
Per #115 I just moved back to beta from stable (got tired of instabilities, especially when they weren't paying off), so that's where I'm seeing this. 8.1, QHD 13.3" at 200X. I can definitely handle both, but in the case of Hangouts, it leaves a weird floating bar a half-inch above the taskbar hovering over everything. It's the minimized conversation window, which looks fine when it's aligned, but is really distracting like this.

Still, the rest actually finally works. So I can put up with these two issues until resolved.

Comment 119 by rad...@gmail.com, Aug 15 2014

Besides Hangouts windows hovering about twice as far from the bottom of the screen as they should, if I move one of them the contents of that window stop being rendered outside the upper left quadrant and the rest of the window no longer responds to clicks. It's as if chrome suddenly thinks the window is half the (linear) size it is.

This is on a 3200x1800 (at 200% scaling) laptop running win 8.1.
Almost there! Just a few small issues:

- When the Chrome window is not maximized, there is a black border around the window
- In the drop down menu in the top right, if you hover over an item with a second menu (such as bookmarks, or help, the second menu slightly overlaps the first menu.
- When you start typing in the address bar (such as typing "chrome:") the suggestions are cut off with a "..." even though there is plenty of room to display the full suggestion.

Tested on 3200x1800 screen, Windows 8.1 Pro

Comment 121 by cpu@chromium.org, Aug 18 2014

@120: I can't repro the 'suggestions' issue in chrome beta (2062.76) with a surface pro at 150%.
#120 are you on canary/dev? Might be https://code.google.com/p/chromium/issues/detail?id=402347 
#121 & #122: Sorry for not mentioning it, I am on Dev: Version 38.0.2125.0 dev-m (64-bit)

#122: that appears to be the issue!
Another affected customer. Very much looking forward to this fix. I received my first HD monitor today, and the first thing I did was download Chrome, and stare at blurry text (because 3200x1800 on a 15" screen requires the font size to be at 125 or 150% or higher)... ouch. :( Please release this soon! :) Setting the properties to ignore HD setting doesn't help (well it does, but it makes everything much too small, and requires continual manual override for the zoom... making more trouble than it saves).
Same here on windows 7 (as I read tickets it seems people are mostly affected on windows 8.x ) . And as a webdev it's began to be very hard to work on Chrome these past few days. Is there a version other than stable I can work with while this being fixed? 

Note : From what I have observe this issue does only appear on my laptop. Chrome dpi on UC seems to be fine. I'm on 1920x980 on both screens. Co-workers on UCs are not experiencing that issue either. 
I am on Version 39.0.2138.3 dev-m (64-bit)

And I have 3200x1800 on main display + 2560x1440 on secondary display. (NVidia Quadro M1100)

Everything seems alright on the main display. 

But when I move the browser window to the secondary display and maximize to full screen, I get blurry vertical overlay on the top and bottom of the web page.

Also when I try to play video in fullscreen, I get glitches during playback (which I do not on IE)

Comment 127 by rad...@gmail.com, Sep 3 2014

So... the extensions issue. Should I open another ticket? Or is someone already working on this?
Just realized this is marked as "fixed." It's not. It's merely much better. Extensions that appear in their own windows still have black bars around them (Keep, for example), floating windows like the App Launcher and the older Hangouts extension sit a half-inch above the taskbar, and the new Hangouts app is basically invisible, except for the top-left corner of a chat window.
Showing comments 29 - 128 of 128 Older

Sign in to add a comment