Don't build property trees whenever opacity of a Layer changes |
|||
Issue descriptionThey should be build only when that Layer doesn't own an effect node, otherwise, updating property trees should be enough.
,
May 13 2016
They also need to be rebuilt if opacity changes from non-1 to 1 or vice-versa (since that affects render surface creation).
,
May 16 2016
,
May 17 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8d6efe2e2ad947cce26006896b87d594a4885c80 commit 8d6efe2e2ad947cce26006896b87d594a4885c80 Author: jaydasika <jaydasika@chromium.org> Date: Tue May 17 15:37:21 2016 cc : Rebuild property trees when opacity changes only if its required. If the change in opacity is from a non-1 value to a non-1 value we need not rebuild property trees as an effect node already exists and we only need to update it. BUG= 611903 CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel Review-Url: https://codereview.chromium.org/1979413002 Cr-Commit-Position: refs/heads/master@{#394131} [modify] https://crrev.com/8d6efe2e2ad947cce26006896b87d594a4885c80/cc/layers/layer.cc [modify] https://crrev.com/8d6efe2e2ad947cce26006896b87d594a4885c80/cc/trees/layer_tree_host.cc [modify] https://crrev.com/8d6efe2e2ad947cce26006896b87d594a4885c80/cc/trees/layer_tree_host_common_unittest.cc
,
May 17 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jaydasika@chromium.org
, May 13 2016