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

I think option 1 is authors would more likely expect when using view timelines. Also, like you said, it's nice if we can have a consistent resolving for ranges across different properties.

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

I suppose if you set only `contain 10%` for `animation-trigger-exit-range-start` it will resolve the end similar to option 1 above.

-- 
GitHub Notification of comment by ydaniv
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11932#issuecomment-2721666085 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 15:28:36 UTC