forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reland Group effects support in cc::AnimationPlayer
Patch https://chromium-review.googlesource.com/c/chromium/src/+/742162 got reverted because it caused cc_unittest failure on CFI bot. This patch fixed the bug. Commit message from the original patch: The current cc/animations logic assumes a single animation has a single keyframe effect and can only affect a single layer. To enable animations with multiple keyframe effects, cc::AnimationPlayer need to support multiple AnimationTickers each corresponding to one keyframe effect. Currently there is a 1:1 relationship between AnimationPlayer and AnimationTicker. This patch is to extend it to 1:n. Here is a summary of changes: - Introduce a sub-class of AnimationPlayer, a.k.a SingleTickerAnimationPlayer, to handle the existing logic (single effect). SingleTickerAnimationPlayer owns only one AnimationTicker as the AnimationPlayer does today. - Currently a AnimationTicker is created upon creating AnimationPlayer. In this patch, tickers are created separately and added to the player afterwards. Tickers that the player owns may belong to different targets therefore the player needs to coordinate with AnimationHost regarding this situation. - Adjust existing unit tests according to the changes above. Bug: 767043 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: If21bad1285c35bbc048fef6b619c8272c0760551 Reviewed-on: https://chromium-review.googlesource.com/890724 Reviewed-by: Ian Vollick <[email protected]> Commit-Queue: Yi Gu <[email protected]> Cr-Commit-Position: refs/heads/master@{#532519}
- Loading branch information
Showing
33 changed files
with
1,915 additions
and
927 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.