- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Oct 2023 10:51:22 +0000
- To: public-css-archive@w3.org
> Looks like something more of an issue for additive cascade to solve. Hmm, I'm not sure if I see how this could help here? What I'm talking about is cases like this: ```HTML <div class="a" timeline-scope: --d> <div class="b" style="timeline-scope: all except(--d)"> <div class="c" style="timeline-view: --c1"></div> <div class="c" style="timeline-view: --c2"></div> <div class="d" style="timeline-view: --d"></div> … </div> <div class="e"></div> </div> ``` Where we could want to have `timeline-scope: all` on the `.b`, so it would encapsulate the scope of all the timelines defined in `.c`, names of which we don't know in advance, but then we could have a different timeline on the `.d` which we would want to reuse outside `.c`, scoping it to the `.a` With just `all` it would prevent the `--d` from being scoped on the `.a`, and the only alternative we would have right now is to mention all the `--c1`, `--c2` etc. explicitly on the `.b`, thus the need for a way to have “all except”. I don't think this is possible with additive cascade, as it would require us to have actual rules targeting the `.b` element which would add the `--c1`, `--c2` etc. in separate declarations, but that won't be possible from inline CSS or via a case where we don't know _what exactly_ would scope our timeline, so we wouldn't know where to make the additions. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9158#issuecomment-1742797028 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 October 2023 10:51:24 UTC