- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Sep 2023 09:51:28 +0000
- To: public-css-archive@w3.org
> I can imagine use-cases where we'd want to completely skip an animation when jumping over the range, for example if we have a long page with multiple scroll-triggered animations, and are landing over some sections via an `#anchor` This can be achieved with what @flackr said above, without a range end the animation will be triggered above, not skipped though. But with `once` behavior the element will already be animated. > ven more, I can imagine the cases for the “range” being very short, like half a screen high, meaning that we'd only want to trigger an animation when we're in the range, for example if we have some kind of “screen” where we'd want to play some animation when that screen is completely in the viewport. Scrolling from either top or bottom, we'd want to trigger the animation only when the screen is completely in the viewport. IIUC this should be covered using `view()` or at least referencing another named view-timeline. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8942#issuecomment-1720996636 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 September 2023 09:51:29 UTC