IMO we should just add this to the manifest:

<dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">permonitorv2, permonitor</dpiAwareness>

That should be simpler and will be enabled for the entire process instead of just Chromium windows (e.g. for native modules). Unfortunately I don't have a multi-monitor setup I can test with.

This is a good fix but should we just cool our heels for M58 since it's out so soon?

@poiru We'll need to add that to the manifest too, but it's unfortunately not enough for Windows 10 versions before the Creators Update, where calling EnableNonClientDpiScaling is required. I tested that scenario. Plus, this patch will come down eventually from Chromium anyway, at which point we will remove this.

@paulcbetts I'm not pushing for merging this, just making it available in case Chromium 58 gets delayed. @kevinsawicki and @zcbenz have that context, so I'll let them decide whether to merge this or not.
🍰

It looks good to me to have this in 1.6.x. 👍