- From: Olga Gerchikov via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 May 2020 15:38:15 +0000
- To: public-css-archive@w3.org
> But thinking about this further, currently the whole point of the pending task is typically to resolve a suitable start time. That's why setting the start time cancels any pending tasks. I was also thinking that perhaps initializing start time in play() should work the same as [setting the start time](https://drafts.csswg.org/web-animations-1/#setting-the-start-time-of-an-animation) regardless of timeline activeness. However I convinced myself otherwise to keep scroll and time linked animations behave similarly in terms of timing of resolving Ready promise and the value of pending flag. In addition, calling play() on pause pending animation has the same effect - hold time unresolved, start time is resolved and Ready promise is resolved asynchronously. > Do we now want animations to remain pending if they don't have an active timeline? If so, we need to update the procedure to set the start time (and possibly other places). If not, we could possibly just call that procedure here instead. Are you referring to finite inactive timelines or in general? If just finite - there is no need to keep the animation pending as calculated current time is unresolved and the animation doesn't have an effect. -- GitHub Notification of comment by ogerchikov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/5059#issuecomment-627423190 using your GitHub account
Received on Tuesday, 12 May 2020 15:38:17 UTC