- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Mar 2025 10:34:15 +0000
- To: public-css-archive@w3.org
I would like it if we could closely match the behavior of Scroll-Driven Animations here. For example, when opening https://scroll-driven-animations.style/demos/image-reveal/css/ for example _(and while making sure both images are not in the viewport – you might have to resize your window)_ and then calling `document.getAnimations()` it returns the two scroll-driven animations even though they are not “in-scrollport”. Those animations are active but in the before phase. `animation-fill-mode: both` is making sure the element is rendered with the `from` keyframe values. To answer the questions asked at the start of the thread, I would assume that: 1. When not triggered yet, the effects of STAs are in their before phase. This to prevent sudden jumps. 2. When calling `getAnimations` STAs are returned because they are impacting rendering of the element. I think this boils down to saying that an animation is also relevant when the `animation-trigger-timeline` is determining things. For `scroll()` or `view()` specifically, that results in a _“non-null associated timeline that is not monotonically increasing”_ used as the animation trigger. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11971#issuecomment-2750811319 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 March 2025 10:34:16 UTC