- From: David A via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Mar 2025 16:46:49 +0000
- To: public-css-archive@w3.org
> Just to be clear, we're saying that STA's with a view/scroll `trigger-timeline` are also relevant, regardless of their fill mode, if either of the following is true: > > * They're trigger is in `idle` state. > * Their `type` is either `repeat` or `alternate`. > > This means their associated effect may not have an actual output in before/after phases of their triggers. This sounds good to me! So contrary to my initial position I think triggers should not prevent their animations from having an effect and should be included in `getAnimations`. One more thing that might be worth calling out is the timing of the [animationstart](https://developer.mozilla.org/en-US/docs/Web/API/Element/animationstart_event) event. The way I'm thinking about it is: say we have an `animation-fill-mode: both/backwards` animation which is yet to trigger. Although the animation's effect is in effect before the animation is triggered, `animationstart` doesn't fire until the animation is triggered and is advancing. The "and is advancing" part means that if the the element has `animation-play-state: paused` it still doesn't fire, until/unless perhaps `animation-play-state` changes to `running`? -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11971#issuecomment-2755075406 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 March 2025 16:46:50 UTC