- From: kevers-google via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Aug 2020 13:40:47 +0000
- To: public-css-archive@w3.org
I'm cool with leaving the play state procedure as is, and updating the test expectations. Unfortunately, most of the behavioral changes were not visible due to lacking mutable timeline support in Blink. For the most part, these changes will not affect behavior in stable releases since mutable timelines have not shipped. One case where a difference is visible: const animation = new Animation(..., null); animation.startTime = ...; This example, will produce 'runniung' on Chrome, and 'idle' on Safari and Firefox (Last I checked, they do not have the unresolved start time constraint in the play state calculation). Having said that, without mutable timeline support this animation is not particularly interesting. Another side effect of the recent play state change is that we will not longer cancel a running CSS transition or animation if the timeline is explicitly set to null. Perhaps this is a good thing as the new behavior is consistent with not suddenly changing state when the timeline becomes inactive (other than no longer being able to be in a finished state). Nonetheless, I believe this is covered by WPT tests that will need to be updated to reflect the behavior of the specced behavior. @flackr Thoughts? -- GitHub Notification of comment by kevers-google Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5400#issuecomment-672877444 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 August 2020 13:40:48 UTC