- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Mar 2025 17:19:47 +0000
- To: public-css-archive@w3.org
> I guess this comes down to something like bikeshedding because both approaches (expanding similar to animation-range or expanding to scroll 100%) give authors the same capabilities. I'm nudged towards having the default range expand to scroll 100% because that lets an author who wants to specify a single point specify a single value :) So what you're saying is not really bikeshedding, but rather resolve on a different default value for `animation-trigger-range-end`, right? Or otherwise have `normal` resolve to `scroll 100%` instead of `cover 100%`? Well we should also take into account not specifying anything, keeping both start and end as `normal` would result as `scroll 0% 100%`, right? IMO having these as defaults kind of defeats the purpose, right? Also, I'd prefer to keep it consistent with `animation-range-end` and `normal` resolving as well, being `cover 100%`. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11932#issuecomment-2755164010 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 17:19:48 UTC