- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 May 2024 14:30:28 +0000
- To: public-css-archive@w3.org
> I think so since animation events are fired from the rendering update code right? The [timelines](https://www.w3.org/TR/web-animations-1/#timelines) section of the web-animations-1 spec covers animation events, in particular: > When asked to update animations and send events for a [Document](https://html.spec.whatwg.org/#document) doc at timestamp now, run these steps: > ... > 4. Let events to dispatch be a copy of doc’s [pending animation event queue](https://www.w3.org/TR/web-animations-1/#pending-animation-event-queue). > 5. Clear doc’s [pending animation event queue](https://www.w3.org/TR/web-animations-1/#pending-animation-event-queue). > ... > 7. [Dispatch](https://dom.spec.whatwg.org/#concept-event-dispatch) each of the events in events to dispatch at their corresponding target using the order established in the previous step. So yep, they are fired as a result of the ["update the rendering" steps](https://html.spec.whatwg.org/#event-loop-processing-model). -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9839#issuecomment-2102778990 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 May 2024 14:30:29 UTC