[csswg-drafts] [web-animations-1] Can the animation be considered *ready* when playback is suspended? (#11519)

cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:

== [web-animations-1] Can the animation be considered *ready* when playback is suspended? ==
The only difference between the execution conditions of the pending [pause](https://drafts.csswg.org/web-animations-1/#pending-pause-task) and [play](https://drafts.csswg.org/web-animations-1/#pending-play-task) tasks is that the pause task requires that playback be *suspended* and the play task requires that playback has *begun*. When the play task conditions are fulfilled, the animation is said to be [ready](https://drafts.csswg.org/web-animations-1/#ready).

So instead of the following in the procedure to pause an animation...

  > 10. Schedule a task to be executed at the first possible moment where both of the following conditions are true:
  >
  >  - the user agent has performed any processing necessary to suspend the playback of `animation`’s associated effect, if any.
  >  - `animation` is associated with a timeline that is not inactive.

... can't we just say that it must be executed as soon as an animation is *ready* and that the animation is ready when playback has begun *or is suspended*?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11519 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 17 January 2025 06:59:20 UTC