Skip to content

Commit 8a31b82

Browse files
graoutsbirtles
authored andcommitted
There is no iterationCount property but there is an iterations property. Fix some non-normative text to use the correct property name. This addresses issue #5096.
1 parent ca556e8 commit 8a31b82

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

web-animations-1/Overview.bs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1691,15 +1691,15 @@ enters the finished state. If notification of the finished state occurred
16911691
synchronously this code would cause the <a>finish event</a> to be queued
16921692
and the <a>current finished promise</a> to be resolved. However, if we
16931693
reverse the order of the two statements such that the
1694-
<code>iterationCount</code> is updated first, this would not happen.
1694+
<code>iterations</code> is updated first, this would not happen.
16951695
To avoid this surprising behavior, notification about the finished state of
16961696
an animation is typically performed asynchronously.
16971697

16981698
<div class='example'><pre class='lang-javascript'>
16991699
var animation = elem.animate({ left: '100px' }, 2000);
17001700
animation.playbackRate = 2;
17011701
animation.currentTime = 1000; // animation is now finished
1702-
animation.effect.updateTiming({ iterationCount: 2 }); // animation is no longer finished
1702+
animation.effect.updateTiming({ iterations: 2 }); // animation is no longer finished
17031703
</pre></div>
17041704

17051705
The one exception to this asynchronous behavior is when the <a>finish an

0 commit comments

Comments
 (0)