@@ -626,6 +626,55 @@ elem.getAnimations()[0].transitionProperty // 'opacity'
626
626
627
627
</div>
628
628
629
+ <h2 id="changes">Changes</h2>
630
+
631
+ <h3 id="changes-fpwd">Changes since Level 1, in First Public Working Draft</h3>
632
+
633
+ <ul>
634
+ <li> Transitions can now occur on discretely-animatable properties. The
635
+ newly-introduced 'transition-behavior' property allows opting in to this behavior.</li>
636
+
637
+ <li> The ''@starting-style'' rule
638
+ (and {{CSSStartingStyleRule}} interface)
639
+ is introduced to allow
640
+ transitions on elements whose style changes
641
+ from not being rendered to being rendered.</li>
642
+
643
+ <li> Interactions with the Web Animations API are more clearly specified:
644
+
645
+ <ul>
646
+
647
+ <li> The {{CSSTransition}} interface is defined.</li>
648
+
649
+ <li> The composite order of the generated animations is defined.</li>
650
+
651
+ <li> The animation class of the generated animations is defined.</li>
652
+
653
+ <li> The cascade level of animation objects that were created from transitions
654
+ and then reused through the Web Animations API is defined,
655
+ along with the concept of [=owning element=] needed to define it.</li>
656
+
657
+ <li> The rules for event dispatch have been specified to explain what happens
658
+ when the animations are seeked or reversed using the Web Animations API.</li>
659
+
660
+ <li> Interaction of the Web Animations API with
661
+ the rules for faster reversing of interrupted transitions
662
+ is specified.</li>
663
+
664
+ <li> [[#requirements-on-pending-style-changes]] are specified.</li>
665
+ </ul>
666
+
667
+ <li> The handling of transitions on elements
668
+ that are no longer being rendered
669
+ is more clearly defined
670
+ (the transitions are canceled
671
+ and removed from the set of completed transitions).</li>
672
+
673
+ </li>
674
+
675
+
676
+ </ul>
677
+
629
678
<h2 id="issues-common">Issues commonly raised as issues with previous levels</h2>
630
679
631
680
<p>
0 commit comments