- From: Sam Weinig via GitHub <noreply@w3.org>
- Date: Tue, 12 May 2026 02:05:48 +0000
- To: public-css-archive@w3.org
> > But even if we assume that effect's target is available at times where resolving rangeStart and rangeEnd happens, it's not clear how that should work. > > Sorry, I may be out of my element here (none intended), can you explain why when you have a target it's still not clear how to resolve values? Heh. What I mean is that there is no specification text that specifies how to take a string, the grammar for a CSS property, and an Element, and produce a TimelineRangeOffset. > > > I think new hooks are needed in one of the base CSS specs (CSS Syntax or CSS Cascade maybe) to specify what it means to parse and resolve a CSS property outside the normal cascade. > > Does "outside of the normal cascade" come from setting the `range*` directly on the animation and not coming from style? Yes. > So the issue is it's not clear how to these values cascade? No. I only mention "outside of the normal cascade", because that is the specified way we know how to resolve things using CSS property grammars. That is, it is well defined how a CSS property in a style rule gets resolved. I can point to spec text that explains how values are resolved, e.g https://www.w3.org/TR/css-cascade-4/#value-stages. -- GitHub Notification of comment by weinig Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13853#issuecomment-4426751913 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 May 2026 02:05:49 UTC