W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2020

Re: [csswg-drafts] [web-animations-1] Play state of an animation with an unresolved timeline (#5400)

From: kevers-google via GitHub <sysbot+gh@w3.org>
Date: Tue, 11 Aug 2020 13:38:54 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-671952617-1597153133-sysbot+gh@w3.org>
We have precedence for the play state being restricted to the idle or paused when the timeline is explicitly null. This was captured in the following WPT test:
  * wpt/web-animations/timing-model/animations/setting-the-timeline-of-an-animation.html
      * After clearing timeline on finished animation it is idle
      * After clearing timeline on running animation it is idle
 
The expectations were updated in  https://chromium-review.googlesource.com/c/chromium/src/+/2150687; however, the expectations no longer align with the test description.  The text associated with these tests could be updated if the new behavior is in fact what we want. 

Though one can think of an animation with a null timeline as one that is always inactive, the distinction is that the animation will never tick until the timeline is changed.  In the case of scroll timelines, the inactive state is transient. 

A benefit of restoring the previous behavior for play state of a null timelines is that we then have consistent behavior across browsers.  Mutable timelines is likely to have cross browser support before scroll timelines. Having said that,  I'm OK with going either way on this, but would like to see consistency with the test expectations and descriptions.



-- 
GitHub Notification of comment by kevers-google
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5400#issuecomment-671952617 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 13:38:56 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:13 UTC