Directly composited value updates should set property node changed bits
When a property node changes in blink, changed bits need to be set on the associated cc property node for damage. Blink has a fast-path for directly updating composited property nodes (see: PropertyTreeManager::DirectlyUpdateScrollOffsetTransform) that marks the cc property node as changed but does not cause a full update. Code was recently added when doing a full update that would unset the changed bit on a cc property node that was directly updated. This patch fixes that bug by not clearing the changed bit of a directly-updated node. This situation could occur if a fast-path direct update and a slow-path update occur in the same frame. This was only noticed on Windows because partial swap is used there which makes the damage bug more visible. Bug: 985729 Change-Id: I483305477d47aef095591c0f7e54720eb06f7827 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721197Reviewed-by:Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#682708}
Showing
Please register or sign in to comment