Use the win32 device scale factor in Chrome ASH on Windows.

Use the win32 device scale factor in Chrome ASH on Windows.

The WinRT interfaces seem to be giving us the wrong values in metro mode. On Windows 8
the IDisplayProperties interface always gives us 100% for the scale factor and a dpi of 96.
On 8.1 it reports incorrect scale factors which cause the content to be displayed shrunk.

Fix is to use the win32 scale factor in ASH and convert the input coordinates to DIP correctly
before passing them to chrome. We also convert the width and height of the window to pixels
using the win32 scale factor before initializing the direct3d swap chain.

BUG=376529
R=cpu

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=273605

[cpu_(ooo_6.6-7.5), 2014-05-27 21:56:27]

looks good but I still want to understand why we need both scales. I'll find
you.

https://codereview.chromium.org/300003002/diff/20001/win8/metro_driver/chrome...
File win8/metro_driver/chrome_app_view_ash.cc (right):

https://codereview.chromium.org/300003002/diff/20001/win8/metro_driver/chrome...
win8/metro_driver/chrome_app_view_ash.cc:408: // via the win32 scale factor
which achieves the needful.
keep up to "scale factor."

[ananta, 2014-05-27 22:46:16]

https://codereview.chromium.org/300003002/diff/20001/win8/metro_driver/chrome...
File win8/metro_driver/chrome_app_view_ash.cc (right):

https://codereview.chromium.org/300003002/diff/20001/win8/metro_driver/chrome...
win8/metro_driver/chrome_app_view_ash.cc:408: // via the win32 scale factor
which achieves the needful.
On 2014/05/27 21:56:27, cpu wrote:
> keep up to "scale factor."
Please elaborate. Did you indicate changing "We scale the point by the ..."
above to "We scale the point to the Win32 scale factor?"

[cpu_(ooo_6.6-7.5), 2014-05-28 23:06:10]

I get it now, the input coordinates are scaled with metro strange values.

lgtm.

[ananta, 2014-05-29 00:50:15]

The CQ bit was checked by ananta@chromium.org

[commit-bot: I haz the power, 2014-05-29 00:50:41]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/ananta@chromium.org/300003002/20001

[commit-bot: I haz the power, 2014-05-29 02:26:29]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)

[commit-bot: I haz the power, 2014-05-29 02:33:49]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-05-29 02:33:49]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)

[ananta, 2014-05-29 18:46:47]

The CQ bit was checked by ananta@chromium.org

[commit-bot: I haz the power, 2014-05-29 18:48:13]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/ananta@chromium.org/300003002/40001

[commit-bot: I haz the power, 2014-05-29 20:34:53]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/7...)

[commit-bot: I haz the power, 2014-05-29 21:34:06]

Change committed as 273605