Re: [csswg-drafts] [web-animations-2][css-animations-2] How should unspecified trigger range boundaries be resolved? (#11932)

> 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 (https://github.com/w3ctag/design-reviews/issues/1011#issuecomment-2460300421) 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."

That is why I added the `auto` value, since `normal` is already specified to have a specific meaning and I did not want to overload that meaning depending on the context. So instead I figured that `auto` in this context means exactly that: "the UA should do what  makes sense, which is match the corresponding value from the default range".

You think it's less appropriate here?

> 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

In this case I'd prefer not having to parse `normal` based on the context. OTOH, I think `auto` _is_ a value that can be parsed differently based on context, so would prefer that value to do a lookup on another property's value. But I'm open to hear otherwise.

> 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.

That is a separate issue I briefly [raised here](https://github.com/w3c/csswg-drafts/issues/8942#issuecomment-2063081488).
I think I'll open a separate issue for that.

-- 
GitHub Notification of comment by ydaniv
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11932#issuecomment-2730254696 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 17 March 2025 17:02:37 UTC