You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A pending animation's play state should reflect the play state it is entering.
For example, a play-pending animation will report 'running' (not idle), a pause-pending animation will report 'paused'.
Likewise for finished animations, we should determine if the animation is finished or not based on the outcome once any pending playback rate is applied.
Consider the following example
constanimation=div.animate({},1000);// playState: running// pending: trueanimation.updatePlaybackRate(-1);// playState: running// pending: true/* Use play() to skip to the end of the animation */animation.play();// playState: finished// pending: trueawaitanimation.ready;// playState: running// pending: true
As you can see, the animation reports 'finished' even though it is about to enter the 'running' state.
By making the algorithm for calculating the play state use the effective playback rate, this will return 'running' instead.
The text was updated successfully, but these errors were encountered:
I'm going to go ahead and merge the PR for this since I don't expect this change to be controversial. If there are any concerns, please let me know and I'll back it out.
A pending animation's play state should reflect the play state it is entering.
For example, a play-pending animation will report 'running' (not idle), a pause-pending animation will report 'paused'.
Likewise for finished animations, we should determine if the animation is finished or not based on the outcome once any pending playback rate is applied.
Consider the following example
As you can see, the animation reports 'finished' even though it is about to enter the 'running' state.
By making the algorithm for calculating the play state use the effective playback rate, this will return 'running' instead.
The text was updated successfully, but these errors were encountered: