- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Sun, 27 Apr 2025 08:26:30 +0000
- To: public-css-archive@w3.org
Since this issue was originally on interaction of `animation-trigger` and `animation-play-state` and we hijacked it to interaction with `cancel()`, I moved that discussion into #11914, and I'll copy the original proposal here again: Proposal - `animation-trigger` does not override the behavior of `animation-play-state`. - If `animation-play-state` is set to `running` then the associated trigger's effects continue as specified. - If the `animation-play-state` is set to `paused` then the associated trigger's effects are overridden and the animation remains paused. - As specified in [CSS Animations](https://drafts.csswg.org/css-animations-2/#animations), any successful call to `play()`/`pause()`/`reverse()` or setting of `startTime` still overrides `animation-play-state`. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12064#issuecomment-2833321683 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 27 April 2025 08:26:31 UTC