Commit 88e77ae7 authored by Scott Violet's avatar Scott Violet Committed by Commit Bot

aura: updates common on device scale factor caching.

BUG=665965
TEST=none

Change-Id: Icf59d9537180eeb11f572d66414e04808be23603
Reviewed-on: https://chromium-review.googlesource.com/c/1316105Reviewed-by: default avatarMichael Wasserman <msw@chromium.org>
Commit-Queue: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605079}
parent 7dcaa9f6
...@@ -352,6 +352,11 @@ class AURA_EXPORT WindowTreeHost : public ui::internal::InputMethodDelegate, ...@@ -352,6 +352,11 @@ class AURA_EXPORT WindowTreeHost : public ui::internal::InputMethodDelegate,
std::unique_ptr<ui::Compositor> compositor_; std::unique_ptr<ui::Compositor> compositor_;
// The device scale factor is snapshotted in OnHostResizedInPixels. // The device scale factor is snapshotted in OnHostResizedInPixels.
// NOTE: this value is cached rather than looked up from the Display as it is
// entirely possible for the Display to be updated *after* |this|. For
// example, display changes on Windows first result in the HWND bounds
// changing and are then followed by changes to the set of displays
//
// TODO(ccameron): The size and location from OnHostResizedInPixels and // TODO(ccameron): The size and location from OnHostResizedInPixels and
// OnHostMovedInPixels should be snapshotted here as well. // OnHostMovedInPixels should be snapshotted here as well.
float device_scale_factor_ = 1.f; float device_scale_factor_ = 1.f;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment