- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Apr 2025 13:41:52 +0000
- To: public-css-archive@w3.org
> But haven't we defined that if a trigger is attached to an animation then it ends up being put in the before phase with a zero time? Meaning that if it has a backwards fill, that will take effect? So in order to remove that does cancel() need to disassociate from the trigger? Currently, any animation has an initial value of `animation-trigger: once auto`, so it has a trigger, and calling `cancel()` on that animation should still set its `currentTime` to unresolved, so that animation's effect will be removed. I think that, by itself, should render the associated trigger effectless. Do you think we need to also explicitly disassociate the trigger? -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12064#issuecomment-2801755888 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 April 2025 13:41:53 UTC