mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
d40f32d326
This isn't spec'ed anywhere (since the whole Web Animations API <-> CSS interaction isn't spec'ed yet) but it seems that changing animation-play-state should not restart an idle animation. If an author calls Cancel() on an animation then that animation should continue to be idle until they call Play()/Pause() from the API. Cancelling an animation and hanging on to it is a purely API-only feature and hence it's reasonable that restoring it from this state is also an API-only feature. One can imagine use-cases such as polyfilling where script wants to remove any CSS Animations/Transitions run by the browser and replace them with something else entirely. In that case, the script can call Cancel() on the animation and be sure that the animation is going to stay out of the way even if something else tweaks the animation-play-state. |
||
|---|---|---|
| .. | ||
| base | ||
| build | ||
| doc | ||
| forms | ||
| generic | ||
| inspector | ||
| ipc | ||
| mathml | ||
| media | ||
| printing | ||
| reftests | ||
| style | ||
| svg | ||
| tables | ||
| tools | ||
| xul | ||
| moz.build | ||