- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2023 03:14:23 +0000
- To: public-css-archive@w3.org
Yes, I agree. `finish` and `end` are different. We should preserve the current behavior where: - the `finish` event fires when the animation's `finished` Promise is resolved. - playing a finished CSS animation backwards fires `animationstart` and `animationend` in that order. That suggests an `end` event, separate to the `finish` event, would be needed if we want Web Animations to have an event matching CSS animations/transitions behavior. Just to check though, why do we need an end event for Web Animations? We've so far avoided adding start/end events to Web Animations because they're tied to animation _effects_ and in a world with group effects, it begs the question of, "Do we dispatch these events for _all_ effects in the effect tree or just the root one?". If it's the former, perhaps they should be _effect_ events, whose event target is an animation _effect_? And what should be dispatched when a parent effect causes a child effect to repeat etc.? If it's the latter, do we need to introduce "start" and "end" concepts to animations, increasing coupling between animations and their root effect's delay properties? -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8544#issuecomment-1461205367 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 March 2023 03:14:25 UTC