Where It All Falls Apart

As with many things in Windows, the operating system is too trusting of developers. Of course not all developers fall into this trap, but many applications in Windows (including many written by Microsoft) don’t follow the best practices on how to deal with High DPI displays. Let’s take a look at one example – VLC player.

VLC 1.0 is what is referred to as a DPI-unaware application. The application was created to render at 96 DPI and it just expects the display to match. This makes the application undersized on a High DPI display, but thanks to DPI Virtualization Windows can automatically scale the application up to match the DPI settings of the display. This does introduce some blurriness to the appearance, but all menu controls and fonts are the correct size for the screen as seen here:

Looking at that image, it’s clearly upscaled but it’s also completely usable. So what’s the issue? VLC is a media player. With DPI Virtualization, media being played back through the application is also rendered at 96 DPI, and then scaled up off screen. This produces a video that appears blurry to the end user, which is not what VLC wants. To correct this issue, the VLC developers changed the application to declare it as System DPI-aware. This disables Windows’ scaling of the application, and Windows expects the application to scale itself. However, in the case of VLC player it doesn’t actually do any scaling at all as you can see in these screen shots of VLC 1.1.1 and the most current version 2.1.3:

 

Here, any of the UI elements that are handled by the operating system are scaled to the correct DPI settings, but the rest of the application is not scaled at all, which results in an application with unequal proportions. I’m not picking on VLC player here – it is just one of many applications that do exactly the same thing. It’s a great example to show the progression of when a coding choice was made to enable the flag and view the results of the change, as older versions of the software are still readily available. Also in VLC’s favor is the fact that their UI elements are somewhat oversized to start with. This could easily have been a design decision that their application was already usable at High DPI, so it’s not worth scaling the UI at this time.

Let’s look at another application which has long been called out for having issues when Windows is run on a High DPI system – Google Chrome. The oddest thing about Chrome not scaling well is that Chrome does actually support High DPI. Chrome OS, Mac OS X, and obviously the Android versions of Chrome all scale well. But on Windows? There are issues. Here’s a screenshot of Google Chrome taken on my Lenovo Yoga 2 Pro at 3200x1800 with Windows scaling set at 200% (the default setting from the factory):

To see the issues, you’ll likely have to open the full resolution version of that screenshot. At first glance all seems pretty nicely scaled with Chrome – the “chrome” of the browser is not tiny, tabs appear to be the correct size – but look at the actual text on the webpage.

With the cropped image, you can instantly see that the font that Chrome is using is not scaling very well. Text in Chrome on a High DPI system is very poor, and defeats the purpose of using a high resolution screen since you actually lose fidelity rather than gain it.

Chrome, unlike many other apps, does have some workarounds to this issue; unfortunately it’s not something the average computer user would ever be able to figure out. First, you have to open chrome://flags setting page and then enable HiDPI Support Windows. Next, you have to right click the Chrome icon on your desktop, choose properties, and then the configuration tab. Here you need to check the box that says “Disable display scaling on High DPI settings” and apply.

What this checkbox does is actually disable the DPI Virtualization on a per-application basis. Chrome will now use XP style scaling. If you don’t check this box, Chrome will disregard the flag in its own settings, and continue to render text very poorly. The only reason I can think of for Chrome to not use the newer DPI awareness API and instead use the old XP style DPI setting request would be because Chrome is still supported on XP. It’s a strange decision though because running a High DPI system on Windows XP is not a great experience. It’s unfortunate for Chrome users because most of them will never know just how poor of an experience they are getting on newer systems. However, with these changes in place, Chrome now renders correctly.

Next, let’s compare Chrome to an application which does follow best practices – Internet Explorer 11. IE11 correctly queries the operating system for the current DPI setting. When it receives the response, it rescales the UI elements as necessary, and then uses its Zoom feature to enlarge the actual web page. The result is a web page that looks exactly as it should.

IE11 also uses the queried DPI level of the operating system to set the default zoom level, so if you are a heavy keyboard user and you like to use Ctrl+0 to get back to 100% zoom, fear not. This still works, but the default zoom will be a higher number than 100% depending on the scaling factor chosen. Here’s another screenshot of IE11 with the resolution set to 3200x1800 and the DPI set at 96 DPI.

At first glance, it looks hilariously bad, but in fact it is doing exactly what it is supposed to. IE has queried the operating system for the DPI level (now set at 96) and scaled correctly to that level. Not all of Microsoft’s applications do this, but most are not as high profile as Internet Explorer.

History of Windows DPI Scaling When It All Goes Really Wrong
POST A COMMENT

114 Comments

View All Comments

  • Lundmark - Wednesday, April 16, 2014 - link

    People who like image quality should get a MacBook. Reply
  • wwwcd - Wednesday, April 16, 2014 - link

    This numbers of DPI or/and PPI(which is the same thing) didn't make me satisfaction. I will wait for 8K(+) resolution for my next large dimensional PC/TV display. Reply
  • aron9621 - Wednesday, April 16, 2014 - link

    Per display DPI scaling in Windows 8.1 is a joke. Try connecting a 180ppi Dell U2414Q and a 96ppi Dell 2413 to your computer, Windows is so dumb it doesn't even detect the correct DPI setting for the monitors, and worse, it doesn't allow you to change it. Oh yes, you can increase/decrease the DPI, but only for BOTH screens simultaneously, it doesn't matter if you have "Let me choose one scaling for all my displays" checked or unchecked, the only difference that setting makes is the way it breaks DPI unaware applications. So you are either stuck with one screen with normal elements and one with tiny ones, or with normal elements on the other screen and giant ones on the former one. And I yet have to figure out how Windows chooses which screen it opens the application on. Reply
  • caywen - Friday, April 18, 2014 - link

    This. Windows seems to have no idea how big my 24" samsung monitor is. I even have samsung's monitor driver installed. In display settings, Windows thinks my Yoga 2 Pro's 13" screen is 4x larger than my 24", presumably because it's still assuming resolution == size.

    I really hope Microsoft fixes this. They should at least provide a way for us to say, "Windows, this monitor size is this big" and for Windows to say "righty ho, now I totally know this display's real DPI."

    I feel like Microsoft is fumbling the ball. They give developers every gun to shoot their foot with, and give users useless tools to mitigate it.
    Reply
  • Gigaplex - Wednesday, April 16, 2014 - link

    "This application is the worst example of usability on a High DPI system that I’ve seen."

    I'd pick small elements over element cropping/overflow any day. It's especially annoying when OK/Cancel buttons on dialogs are off-screen because their location wasn't calculated correctly.
    Reply
  • aeeroO - Wednesday, April 16, 2014 - link

    960x480 WHAT KIND OF SORCERY IS THAT? Every apple fanboy knows it's 960x640...Anand, where are you? Reply
  • StrangerGuy - Wednesday, April 16, 2014 - link

    I find it especially baffling how could people even defend DPI laziness...in mid 2014.

    What, you don't like progress, or are you still living in 2000?
    Reply
  • valhar2000 - Wednesday, April 16, 2014 - link

    So, once again, Microsoft gets blamed for the mistakes of other software developers. If only Adobe had a letter "s" in their name that could be easily replaced with a "$"... Reply
  • e_sandrs - Wednesday, April 16, 2014 - link

    You could use the Euro sign for the e and/or the Thai Baht for the b and/or the Vietnam Dong for the d? That's the best I could do. :)

    A₫o฿€
    Reply
  • berger0 - Wednesday, April 16, 2014 - link

    Anyone know a work around to fix Chrome? In Chrome 35 they removed the HiDPI flag. I found some post that had me put the flag in the registry, but chrome looks really bad now. Anyone else running Chrome Beta or Canary seeing this issue? I am running the YogaPro 2 Reply

Log in

Don't have an account? Sign up now