mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-24 02:35:41 +00:00
7e96375f18
When we are composing style for the Animations level of the cascade, if we have transitions-level animations, we *also* need to compose them if we have animations-level animations that build on top of them using additive or accumulative composite modes. However, we should not build those transitions-level animations unless they will be built on or overridden by a regular animations-level animation. Otherwise we will end up with transitions-level animations in the animations-level and while transitions-level will override the animations-level in the cascade, once the transition finishes there will be nothing to remove the cached animations-level animation rule. MozReview-Commit-ID: LaRabzDSsO5 --HG-- extra : rebase_source : 256efb5779a8cbcc8ae906295b40b160a55641c9
10 lines
763 B
Plaintext
10 lines
763 B
Plaintext
== transitions-inline-already-wrapped-1.html transitions-inline-ref.html
|
|
== transitions-inline-already-wrapped-2.html transitions-inline-ref.html
|
|
== transitions-inline-rewrap-1.html transitions-inline-ref.html
|
|
== transitions-inline-rewrap-2.html transitions-inline-ref.html
|
|
== stacking-context-opacity-lose-to-animation.html stacking-context-transition-ref.html
|
|
== stacking-context-transform-lose-to-animation.html stacking-context-transition-ref.html
|
|
== stacking-context-opacity-wins-over-important-style.html stacking-context-transition-ref.html
|
|
== stacking-context-transform-wins-over-important-style.html stacking-context-transition-ref.html
|
|
== transition-and-animation-with-different-durations.html transition-and-animation-with-different-durations-ref.html
|