| commit | 166841586ac4caae837b561720cf55e6d0b630d2 | |
| author | aelias@chromium.org <aelias@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Fri, 13 Jun 2014 01:41:12 +0000 (13 01:41 +0000) | ||
| committer | aelias@chromium.org <aelias@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Fri, 13 Jun 2014 01:41:12 +0000 (13 01:41 +0000) | ||
| tree | c71f93b9eda9196003016311b576d1d26aa5480e | treesnapshot (tar.gz zip) |
| parent | 255d4a9cbd90a498ba41bf844674bc27cc648df9 | commitdiff |
Clobber frame_data->device_scale_factor to 1 on Android.
On Android, the browser compositor lies to CC about the
device_scale_factor (always setting it to 1), because it places its
layers in physical pixel space. Because of that, the delegated device
scale inversion added in https://codereview.chromium.org/311253004 does
the wrong thing. Rather than cancelling the inversion with other
transforms, the simplest fix is to lie about the frame_data
device_scale_factor as well.
BUG=383572,383436,384134
NOTRY=true
Review URL: https://codereview.chromium.org/336433003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276882 0039d316-1c4b-4281-b951-d872f2087c98
On Android, the browser compositor lies to CC about the
device_scale_factor (always setting it to 1), because it places its
layers in physical pixel space. Because of that, the delegated device
scale inversion added in https://codereview.chromium.org/311253004 does
the wrong thing. Rather than cancelling the inversion with other
transforms, the simplest fix is to lie about the frame_data
device_scale_factor as well.
BUG=383572,383436,384134
NOTRY=true
Review URL: https://codereview.chromium.org/336433003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276882 0039d316-1c4b-4281-b951-d872f2087c98
| android_webview/browser/hardware_renderer.cc | diffblobblamehistory | |
| content/browser/renderer_host/render_widget_host_view_android.cc | diffblobblamehistory |