diff options
| author | jaydasika <jaydasika@chromium.org> | 2015-10-07 10:59:52 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-10-07 18:01:28 +0000 |
| commit | 0c1fd60a253036b1add346cbacc306eac30c6eaf (patch) | |
| tree | 5c28bcb03f06f5519479edbb2b62e26a802dcede /cc/trees/property_tree.cc | |
| parent | e11579c50dd772ee08d969dd4d54bae4b064999a (diff) | |
| download | chromium_src-0c1fd60a253036b1add346cbacc306eac30c6eaf.zip chromium_src-0c1fd60a253036b1add346cbacc306eac30c6eaf.tar.gz chromium_src-0c1fd60a253036b1add346cbacc306eac30c6eaf.tar.bz2 | |
Update page scale factor in property before calling ComputeVisibleRects
When page scale factor is updated directly on the active tree using
LayerTreeImpl::SetPageScaleOnActiveTree, the property trees on pending
tree are not updated. At this point, if we compute draw properties on
pending tree, there is a mismatch between the properties computed from
property trees and CDP because CDP uses the new value (as page scale
factor itself is a synced property) and pending tree property trees
use the old value.
This CL updates page scale factor in property trees before we call
ComputeVisibleRectsUsingPropertyTrees.
BUG=538624
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Review URL: https://codereview.chromium.org/1382353004
Cr-Commit-Position: refs/heads/master@{#352888}
Diffstat (limited to 'cc/trees/property_tree.cc')
| -rw-r--r-- | cc/trees/property_tree.cc | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/cc/trees/property_tree.cc b/cc/trees/property_tree.cc index 86a776a..cb6311a 100644 --- a/cc/trees/property_tree.cc +++ b/cc/trees/property_tree.cc @@ -23,7 +23,8 @@ template <typename T> PropertyTree<T>::~PropertyTree() { } -TransformTree::TransformTree() : source_to_parent_updates_allowed_(true) {} +TransformTree::TransformTree() + : source_to_parent_updates_allowed_(true), page_scale_factor_(1.f) {} TransformTree::~TransformTree() { } |