- From: David A via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Mar 2025 17:21:02 +0000
- To: public-css-archive@w3.org
> Also notice that exit range properties allow an [auto](https://drafts.csswg.org/css-animations-2/#valdef-animation-trigger-exit-range-start-auto) value as default which falls back to the corresponding value of the default range, and not to normal. Ah yes, perhaps another issue worth resolving on: I agree that it would be nice to have a default value for the exit range boundaries that says "match the default range" but I know there's been some concern ([example](https://github.com/w3c/csswg-drafts/issues/11173), ) in the past about specifying `auto` in a way that doesn't mean "user agent should do what makes sense". This doesn't mean that user agents can't treat `auto` this way, but maybe is a reason to instead consider using `normal` to mean "match the default range." This would mean `normal` for `animation-trigger-exit-range` is different from `normal` for `animation-range` but I think this wouldn't be too problematic a difference for developers and may even be the more meaningful option if we establish some relationship between the default and exit ranges like [11910](https://github.com/w3c/csswg-drafts/issues/11910) discusses. It would also mean that an author that means to specify "cover" range (which "normal" would have meant) as the exit range but not as the default range in the shorthand (`animation-trigger`) would need to specify the first 2 longhands, `animation-trigger-range-start` and `animation-trigger-range-end`, and "cover", i.e. they couldn't write `animation-trigger-range: contain 0%` or `animation-trigger-range: contain 0% contain 100%`. They would have to write `animation-trigger-range: contain 0% contain 100% cover`... but this would be the same with `auto` if the exit-range properties default to `auto`. -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11932#issuecomment-2722077924 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 March 2025 17:21:03 UTC