Scale bounds from dip to pixels in CompositorFrame in content::MusBrowserCompositorOutputSurface.

Scale bounds from dip to pixels in CompositorFrame in
content::MusBrowserCompositorOutputSurface since 
CompositorFrames we submit to the display-manager need 
to be in physical pixel-space.

BUG=680982
TEST=manual (--force-device-scale-factor=2)

Review-Url: https://codereview.chromium.org/2644983002
Cr-Commit-Position: refs/heads/master@{#445137}
Committed: https://chromium.googlesource.com/chromium/src/+/5ab7d1bfe8bf1024ea1459002c179a8cd24f6f29

[riajiang, 2017-01-20 02:48:31]

Description was changed from

==========
Scale bounds from dip to pixels in CompositorFrame in
content::MusBrowserCompositorOutputSurface.

BUG=680982
TEST=manual (--force-device-scale-factor=2)
==========

to

==========
Scale bounds from dip to pixels in CompositorFrame in
content::MusBrowserCompositorOutputSurface.

BUG=680982
TEST=manual (--force-device-scale-factor=2)
==========

[riajiang, 2017-01-20 02:50:14]

The CQ bit was checked by riajiang@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-20 02:50:42]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[riajiang, 2017-01-20 03:01:19]

riajiang@chromium.org changed reviewers:
+ sadrul@chromium.org, sky@chromium.org

[riajiang, 2017-01-20 03:01:20]

Hi sadrul@ and sky@, both browser and renderer show up correctly after this
change. I don't quite understand why browser had the correct size even before
this change; and renderer still has half the expected height (when printing out
ServerWindow tree using ctrl+shift+alt+s or client side using ctrl+shift+alt+w).
But everything on screen seem to have the right size and expected behavior now.
PTAL, thanks!

[commit-bot: I haz the power, 2017-01-20 03:33:37]

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

[commit-bot: I haz the power, 2017-01-20 03:33:38]

Dry run: This issue passed the CQ dry run.

[sky, 2017-01-20 16:42:19]

LGTM but but I'm not an owner. Sadrul is though.

Thanks for tracking this down!

[sadrul, 2017-01-20 19:11:26]

lgtm

[sadrul, 2017-01-20 19:12:55]

Can you update the CL desc. to say that CompositorFrames we submit to the
display-manager need to be in physical pixel-space?

[riajiang, 2017-01-20 19:40:13]

Description was changed from

==========
Scale bounds from dip to pixels in CompositorFrame in
content::MusBrowserCompositorOutputSurface.

BUG=680982
TEST=manual (--force-device-scale-factor=2)
==========

to

==========
Scale bounds from dip to pixels in CompositorFrame in
content::MusBrowserCompositorOutputSurface since 
CompositorFrames we submit to the display-manager need 
to be in physical pixel-space.

BUG=680982
TEST=manual (--force-device-scale-factor=2)
==========

[riajiang, 2017-01-20 19:41:02]

The CQ bit was checked by riajiang@chromium.org

[commit-bot: I haz the power, 2017-01-20 19:41:40]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-20 19:45:41]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1484941262805550, "parent_rev":
"b53feae503c3d2a12f9f07c40dad53229bc8bbde", "commit_rev":
"5ab7d1bfe8bf1024ea1459002c179a8cd24f6f29"}

[commit-bot: I haz the power, 2017-01-20 19:46:10]

Description was changed from

==========
Scale bounds from dip to pixels in CompositorFrame in
content::MusBrowserCompositorOutputSurface since 
CompositorFrames we submit to the display-manager need 
to be in physical pixel-space.

BUG=680982
TEST=manual (--force-device-scale-factor=2)
==========

to

==========
Scale bounds from dip to pixels in CompositorFrame in
content::MusBrowserCompositorOutputSurface since 
CompositorFrames we submit to the display-manager need 
to be in physical pixel-space.

BUG=680982
TEST=manual (--force-device-scale-factor=2)

Review-Url: https://codereview.chromium.org/2644983002
Cr-Commit-Position: refs/heads/master@{#445137}
Committed:
https://chromium.googlesource.com/chromium/src/+/5ab7d1bfe8bf1024ea1459002c17...
==========

[commit-bot: I haz the power, 2017-01-20 19:46:11]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/5ab7d1bfe8bf1024ea1459002c17...