- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Sat, 11 Mar 2023 02:10:44 +0000
- To: public-css-archive@w3.org
> CSS Animations has an [`animationiteration` event](https://drafts.csswg.org/css-animations/#eventdef-globaleventhandlers-animationiteration) which fires between iterations. The `animationend` event only fires after all of the iterations. Yes, but if the _parent_ iterates, the child will also _effectively_ iterate despite having an iteration count of 1. As a result, the child animation will finish and start again but, depending on the length of the parent group and frame rate, we will either see an `animationend` followed by an `animationstart` or no events at all. > I think you may want both abilities, as I'm sure some developers are interested in whether the whole set of animations (whatever those animations happen to be) has ended. The strawman proposal was that we could dispatch events at effects such that they bubble up to the animation so you can listen at either point. Doing that would mean that once you have nested effects, however, if you're listening at the animation level and were only interested in when the root effect had ended, you'd need to filter our events from child effects. That's a pretty similar situation to where we are today with CSS animation/transition events, however, where you need to be careful to ignore events from child elements and unrelated animations/transitions. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8544#issuecomment-1464792249 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 11 March 2023 02:10:46 UTC