As a side note, my user agent says I am using a Canary build, however, I have not personally experienced the issue.

As it turns out, Chrome is now in proportion with the rest of Windows' UI at 125% DPI. Many users seem to be complaining that their UI is way too large. Changing the settings in Windows 10 solves the issue. 

I assume this is NOT a bug, however the community doesn't seem to be thrilled.

Unable to reproduce the issue on Windows 10 (Laptop) using chrome stable #54.0.2840.59 and latest canary #56.0.2895.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Launched chrome browser.
2. Opened wikipedia and inspected dev tools.
3. Checked for DevicePixelRatio value in dev tools which appeared as 1.25
4. Observed that chrome scaled properly without any issues.

tsrwebgl@ - Could you please check this issue on latest canary #56.0.2895.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.
		

Deleted: 656234.mp4 1.9 MB

	656234.mp4 1.9 MB View Download

This refers to Windows display scaling, not Chrome.

Deleted: Untitled Screencast.webm 6.3 MB

	Untitled Screencast.webm 6.3 MB View Download

GPF links: https://productforums.google.com/forum/#!topic/chrome/TChO9wLx9hk;context-place=topicsearch/author$3Ame$20large https://productforums.google.com/forum/#!topic/chrome/sshydTDZTgw;context-place=forum/chrome https://productforums.google.com/forum/#!topic/chrome/IGSRKaXrn60;context-place=topicsearchin/chrome/large%7Csort:date https://productforums.google.com/forum/#!topic/chrome/XJ72G98VKC0;context-place=topicsearchin/chrome/large%7Csort:date https://productforums.google.com/forum/#!topic/chrome/bv2MZGhU4vE;context-place=topicsearchin/chrome/large%7Csort:date https://productforums.google.com/forum/#!topic/chrome/FLXs5lYQyBY;context-place=topicsearchin/chrome/large%7Csort:date

And the list goes on...

On the GPF, Bill Mastripolito claims to have a workaround:

"If your chrome has just made everything larger with todays update, here is your solution to get it back to normal.
Right click on your chrome icon, then click on properties, click in the "target" box, go to the end of that field which should end with " put a space after that then paste the following after that space

--high-dpi-support=1 --force-device-scale-factor=1

then click ok then close and reopen chrome and you should be back to normal."

Please note this is regression. People started complaining about this as soon as M54 was released. The Last M53 stable release did not have this issue.

It appears the "fix" doesn't work for all users: https://productforums.google.com/forum/#!topic/chrome/bOutWdick1M;context-place=mydiscussions

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I contend that despite this being intentional, it is fact is a bug.   Here's the thing Windows DPI scaling is for the UI.  The way the Chrome team has implemented this impacts not only the Chrome UI but also the content inside Chrome.  This causes Chrome to work differently than other programs on Windows.  The perfect example being pictures.   Set Windows DPI to 125% or 150% open a picture in the program of your choice.  The picture will not change size regardless of your Windows scaling setting.  Now open a picture in Chrome, depending on your Windows scaling the picture itself will be scaled.  Working differently than the other programs is what I call a bug, not a bug fix.  

1. The Chrome implementation of (now) correctly observing Window's DPI scaling should have applied to the Chrome UI only, not the browser contents.    

2. Additionally, this was a major usability change to how Chrome has worked for years.  An interest in General usability alone, makes it seem common sense that allow with this change users should be given a way to preserve the usability they are accustomed to having.  I'm disappointed in the team's resistance to releasing a way of controlling scaling. 

I wanted to add that the present best work around creating a custom shortcut with this commandline switch:

--high-dpi-support=1 --force-device-scale-factor=1 

WORKS VERY POORLY.

Here are some issues:

*There is no way to enforce that Chrome opens using the custom shortcut.  This means that opening any links directly will open the system Chrome file, bypassing the custom shortcut switch.
*The first instance of Chrome appears to set the scaling behavior takign precendance over the other instances.  This means if Hangouts, Keep or Drive automatically start at the login the custom shortcut will not work.  The solution is to close all instance of Chrome, then re-open Chrome using the custom shortcut.  However, it's not as simple as it sounds because Chrome can run as a background process.  So you often needs to open Taskmanager, terminate all Chrome process, then re-open Chrome using the Custom shortcut.

In sum this creates a poor end user experience and an annoyance for support staff such as myself who have no good solutions to offer.  I'm used to Chrome being better than this. 

As comment #2 stated, this was changed intentionally so that Chrome is in proportion with the rest of Windows' UI. There is more context in  bug 410696 , but the summary is that 125% scaling was disabled back in M37 due to our poor handling of that scale factor. But we've improved a lot of the issues that were causing trouble back then.

For reference, if you would like to change your system's scaling to 100%:

On Windows 7, go to Control Panel>Appearance and Personalization>Display ("Make text and other items larger or smaller") and click the radio button next to "Smaller"

On Windows 10, go to Settings>System>Display and drag the slider underneath "Change the size of text, apps, and other items" so that it reads 100%.

Suggesting for people to set Windows Scaling back to 100% is not a solution.  This causes Windows system text on High resolutions displays to be too small for older eyes.  The problem will only be worse once 4k becomes more common.

All we're asking for is a way to manually override the scaling in Chrome, so it can ignore the Windows scaling.  

You admit that Chrome handles 125% scaling poorly, so why then would you force it users who need larger text in the Windows UI?