- From: Sam Weinig via GitHub <noreply@w3.org>
- Date: Sat, 09 May 2026 21:45:21 +0000
- To: public-css-archive@w3.org
> Well, the range* properties belong to an animation, which has an associated effect, and effect has a target Element. It's not abstract like a DOMMatrix. Shouldn't that solve the "how"? I don't think an instance of `Animation` always has an `effect`, (the `effect` is optional in the constructor) and similarly, an `effect` doesn't always have a `target` element (the constructor for `KeyframeEffect` allows passing in a null `target`). It's plausible that `rangeStart` and `rangeEnd` are never utilized if there is no `effect` and/or `target`, but that is not totally clear to me. 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. 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. -- GitHub Notification of comment by weinig Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13853#issuecomment-4413741580 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 9 May 2026 21:45:22 UTC