- From: Antoine Quint via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Jan 2025 11:05:29 +0000
- To: public-css-archive@w3.org
graouts has just created a new issue for https://github.com/w3c/csswg-drafts: == [web-animations-2] [scroll-animations] setting an animation's timeline to a progress-based timeline should create a new `ready` promise == Step 9 of the [setting the timeline of an animation](https://drafts.csswg.org/web-animations-2/#setting-the-timeline) procedure deals with the case where the new timeline is progress-based is to set the _auto align start time_ flag to true. When this flag is true, the animation's start time may be computed to a new value based on the associated timeline's current time. Furthermore, this procedures schedules a _pending play task_ if the animation had finished or was running. Since the start time will be set when the timeline is updated next, it seems to me that we should also reset the `ready` promise in the case where we schedule a pending play task. In fact, some existing scroll-animations tests actually expect this behavior: - [scroll-animations/css/animation-timeline-ignored.tentative.html](https://github.com/web-platform-tests/wpt/blob/master/scroll-animations/css/animation-timeline-ignored.tentative.html) - [scroll-animations/scroll-timelines/setting-timeline.tentative.html](https://github.com/web-platform-tests/wpt/blob/master/scroll-animations/scroll-timelines/setting-timeline.tentative.html) Chrome passes those tests and seems to implement this behavior. I think this is an oversight in the spec. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11465 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 January 2025 11:05:30 UTC