Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Avoid calling CompositorPropertyAnimationsHaveNoEffect when effect->I…
…sCurrent() is false. Being stricter about compositing only the relevant property tree nodes for relevant animations (https://crrev.com/c/3307117) has made the DCHECK()s in CompositorPropertyAnimationsHaveNoEffect more sensitive. In particular, those DCHECK()s, which ensure that either no properties of an animation or all properties of an animation are composited, will sometimes (prior to this change) run for animations that are not current. This is a case where other animations might have caused some (but not all) of the properties to be composited, yet this animation (in UpdateAnimationFlagsForAnimation in css_animations.cc) will not set the flags for this animation that cause the properties it animates to be composited. Avoiding calling CompositorPropertyAnimationsHaveNoEffect in such cases avoids this problem. Fixed: 1319304 Change-Id: If3db29b98ce319c57e27acbe2f47d7319ec8230b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3609191 Commit-Queue: David Baron <[email protected]> Reviewed-by: Robert Flack <[email protected]> Cr-Commit-Position: refs/heads/main@{#997837}
- Loading branch information