- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Aug 2020 03:28:25 +0000
- To: public-css-archive@w3.org
> however, it does break the play state for cases where the timeline is unresolved. Explicitly setting the start time of an animation with an unresolved timeline should leave the animation in an idle state. I'm not sure I quite follow this part. I _think_ it actually makes sense to me that the animation is finished/running at this point? > Suggesting the following change to play state: > > All of the following conditions are true: > The current time of animation is unresolved, and > the start time of animation is unresolved **or the timeline is unresolved**, and > animation does not have either a pending play task or a pending pause task, > > → idle Is there precedent for distinguishing between the lack of an associated timeline and an associated but inactive timeline? I thought we always treated those two as the same? (i.e. the lack of an associated timeline can be thought of as being associated with a "null timeline" that is always inactive). > If the timeline is explicitly set to null, should the play state be allowed to be in a running state? I _think_ so? -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5400#issuecomment-671703122 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 August 2020 03:28:27 UTC