andruud
andruud
This should be well defined now. Only anchor queries from within the flat-tree subtree of `#scoper` can "see" `--anchor`. So it's not visible in the outer scope, except when the...
I am tempted to say that the web component author shouldn't have blocked all anchors if all anchors shouldn't be blocked. If you're worried that this is a bad situation...
OK, that makes sense. Agenda+ to see if we can make `all` tree-scoped.
> It covers nesting feature detection via @supports, which is a pretty valuable feature for web developers, it would be nice if that behaved consistently across browsers. Makes sense, but...
Looks good to me as well. > Chrome is failing the first test I've known for a while that <general-enclosed> got messed up after some refactor, https://crbug.com/40237918.
The latest resolution invalidates ``'s reason to exist: `@container (width > 100px) or style(--x: nice) or future-thing(nice) {}` now can't evaluate to true anymore, so it might as well fail...
Ah. In that case, maybe [the example I wrote in this PR](https://github.com/w3c/csswg-drafts/pull/6688/files#diff-0546daf72b67dc8a6507c7e786b3fbc0ff55547076cebb0bd294dbcf4c602863R878) isn't so meaningful, since commitStyles won't trigger a transition for a separate and more specific reason.
> Edit: or maybe just let :root match the host, while in :host-context(:root) it refers to the actual root (or host's host)? Hmm, this is basically the same as allowing...
Yeah, at least if we choose the path forwards carefully, it should be easy. That carefully chosen path could be something like: * When you see an `if()` in a...