- From: kevers-google via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Aug 2020 18:07:07 +0000
- To: public-css-archive@w3.org
cc @birtles @ogerchikov @majido @flackr
Related to issue: https://github.com/w3c/csswg-drafts/issues/2066
Changes to how play state is calculated for supporting scroll timelines introduced changes in the behavior of set timeline. These side effects would not have been visible in WPT tests in Blink since setting the timeline was not supported.
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
If the timeline is explicitly set to null, should the play state be allowed to be in a running state?
With this change, the changes in support of scroll timelines do not introduce inconsistencies between browsers for null timelines.
--
GitHub Notification of comment by kevers-google
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5400#issuecomment-670090199 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 August 2020 18:07:08 UTC