- From: David A via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Apr 2025 14:16:43 +0000
- To: public-css-archive@w3.org
> And for: `animation-trigger-range-start: entry 20%; animation-trigger-exit-range-start: normal` You'll get: `animation-trigger-range-start: entry 20%; animation-trigger-exit-range-start: cover 0%`. > Right, I was mistaken about the meaning of `normal`. I thought `contain normal` in the `animation-range` context was `contain contain` but it is `contain cover`, matching your example. > So for: animation-trigger-range-start: entry 20%; animation-trigger-exit-range-start: auto > You'll get: animation-trigger-range-start: entry 20%; animation-trigger-exit-range-start: entry 20%. Because of the way I thought `normal` worked, I thought `auto` should try to do something like that too. But since that isn't the case, I think it makes sense that `auto` simply resolves as the default range. Though now I wonder if this simpler definition calls for a more precise keyword than `auto` since the behavior is always the same. Maybe `default`.. `match`? -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11932#issuecomment-2786607390 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 April 2025 14:16:44 UTC