Disable calls to SetProcessDPIAware under Win8.1.

Disable calls to SetProcessDPIAware under Win8.1. 

BUG=160457, 329143

[girard, 2014-01-13 22:26:07]

This patch addresses the M32 high dpi failure.

[ananta, 2014-01-13 22:28:29]

Is this part of always initializing DPI awareness in chrome?

[girard, 2014-01-13 22:35:00]

On 2014/01/13 22:28:29, ananta wrote:
> Is this part of always initializing DPI awareness in chrome?

Related, yes.

In this case, we never initialize DPI on 8.1. Users who run with
--high-dpi-support=1 flag end up with a broken system (As described in issue
160457#53)
This patch will disable DPI for those users.

[girard, 2014-01-13 22:36:46]

On 2014/01/13 22:35:00, girard wrote:
> On 2014/01/13 22:28:29, ananta wrote:
> > Is this part of always initializing DPI awareness in chrome?
> 
> Related, yes.
> 
> In this case, we never initialize DPI on 8.1. Users who run with
> --high-dpi-support=1 flag end up with a broken system (As described in issue
> 160457#53)
> This patch will disable DPI for those users.

Note: This patch is intended for M32 only (not for ToT)

[ananta, 2014-01-13 22:37:23]

Win 8.1 was broken for high DPI for these users because doing it in chrome.dll
was too late?. So this patch would bring back blurry chrome until we have the
full set of fixes in M34?

[girard, 2014-01-13 22:41:50]

On 2014/01/13 22:37:23, ananta wrote:
> Win 8.1 was broken for high DPI for these users because doing it in chrome.dll
> was too late?. So this patch would bring back blurry chrome until we have the
> full set of fixes in M34?

Correct. (Although perhaps we can hope for a fix in M33;)

[ananta, 2014-01-13 22:42:28]

lgtm

[girard, 2014-01-14 22:44:14]

+ben for owners. PTAL

[Ben Goodger (Google), 2014-01-21 17:36:15]

lgtm