- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Sep 2023 18:53:02 +0000
- To: public-css-archive@w3.org
> The polyfill implements this by changing the "fill" behavior of the implicitly created animation. We could implement different behavior for scroll trigger as I do think a common case will be to want a single trigger point forever. Doesn't sound right to me. I don't think we have anything else that behaves this way (as in same property and value inflate differently depending on context) right? > As for ways to represent this, animation-iterations supports an infinite value, we could support the same for animation-range. Alternately, we have talked about having a phase for the entire range of the scroller in other issues (https://github.com/w3c/csswg-drafts/issues/8672#issuecomment-1545980510 and https://github.com/w3c/csswg-drafts/issues/8578#issuecomment-1540705525) but I had a hard time getting consensus on this being the range when no range name was specified. I like the `scroll` range proposal. Although it's a bit limited since `view()` is limited to `nearest` scroller only, but can be worked around with a named range on a separate element. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8942#issuecomment-1730128285 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 September 2023 18:53:04 UTC