- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Sep 2022 12:44:04 +0000
- To: public-css-archive@w3.org
> But idle animations is a good point. We'll need to wait for the step which processes all new animations after it has been set up (either in CSS or JS) to ensure it changes from idle to running state. For example if its start time is unresolved. Does that happen as a part of update-the-rendering loop? After that can an animation still be in idle state? Animations that have pending play or pause task are not reported as idle so they will still be idle after the updating the rendering. Idle animations are those which have never been scheduled to play (e.g. just created with the `Animator` ctor without ever setting the start time or calling `play()`) or which have been cancelled for some reason. If the start time is unresolved because the the author has called `play()` (or the CSS bindings have caused it to be played) but the browser has yet to determine the start time (which it typically resolves after painting the assets for the first frame), then it will still be reported as running, not idle, because it has a pending play task. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7785#issuecomment-1260850426 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 September 2022 12:44:05 UTC