@@ -534,7 +534,7 @@ The connection between <a>time values</a> and wall-clock milliseconds
534534may be obscured by any number of transformations applied to the value as
535535it passes through the time hierarchy.
536536
537- <p class="annotation ">
537+ <p class="note ">
538538In the future there may be timelines that are based on scroll position
539539or UI gestures in which case the connection between time values and
540540milliseconds will be weakened even further.
@@ -762,7 +762,7 @@ if <var>animation</var>'s <a>previous current time</a> is <a
762762lt="unresolved"> resolved</a> , the procedure to <a>silently set the current
763763time</a> of <var> animation</var> to <a>previous current time</a> is run.
764764
765- <div class="annotation ">
765+ <div class="note ">
766766
767767This step makes the behavior when an <a>animation</a> 's <a>timeline</a> becomes
768768<a lt="inactive timeline">inactive</a> consistent with when it is
@@ -906,7 +906,7 @@ an animation, <var>animation</var>, to <var>seek time</var> is as follows:
906906 make <var> animation</var> 's <a lt="animation start time">start time</a>
907907 <a>unresolved</a> .
908908
909- <p class=annotation >
909+ <p class=note >
910910 This preserves the invariant that when we don't have an active timeline it
911911 is only possible to set <em> either</em> the <a>animation start time</a>
912912 <em> or</em> the animation's <a>current time</a> .
@@ -948,7 +948,7 @@ is as follows:
948948 time</var> is <a lt="unresolved">resolved</a> , make <var> animation</var> 's
949949 <a>hold time</a> <a>unresolved</a> .
950950
951- <p class=annotation >
951+ <p class=note >
952952 This preserves the invariant that when we don't have an active timeline it
953953 is only possible to set <em> either</em> the <a>animation start time</a>
954954 <em> or</em> the animation's <a>current time</a> .
@@ -1176,7 +1176,7 @@ as CSS Animations [[CSS-ANIMATIONS-1]].
11761176 <var> animation</var> with the <var> did seek</var> flag set to false,
11771177 and the <var> synchronously notify</var> flag set to false.
11781178
1179- <div class="annotation ">
1179+ <div class="note ">
11801180 Note that the order of the above two steps is important
11811181 since it means that an animation with zero-length <a>target
11821182 effect</a> will resolve its <a>current ready promise</a>
@@ -1739,7 +1739,7 @@ The procedure to <dfn>reverse an animation</dfn> of <a>animation</a>
173917392. <a>Silently set the animation playback rate</a> of
17401740 <var> animation</var> to <code> −<a>animation playback rate</a> </code> .
17411741
1742- <div class="annotation ">
1742+ <div class="note ">
17431743 This must be done silently or else we may end up resolving
17441744 the <a>current ready promise</a> when we do the compensatory
17451745 seek despite the fact that we will most likely still have a
@@ -3988,7 +3988,7 @@ interface AnimationEffectReadOnly {
39883988};
39893989</pre>
39903990
3991- <div class="annotation ">
3991+ <div class="note ">
39923992In future, we may expose <code> any onupdate (double? progress,
39933993double currentIteration, Animatable? target, any
39943994underlyingValue)</code> so that the animation effects can be driven
@@ -4559,7 +4559,7 @@ interface KeyframeEffect : KeyframeEffectReadOnly {
45594559
45604560 </div>
45614561
4562- <p class="annotation ">
4562+ <p class="note ">
45634563 This method is largely provided for consistency with
45644564 {{KeyframeEffect(source)}} .
45654565 </p>
0 commit comments