- From: James Stuckey Weber via GitHub <noreply@w3.org>
- Date: Mon, 09 Mar 2026 14:07:44 +0000
- To: public-css-archive@w3.org
> You don't need to pick the first `<option>` to get a reference to a descendant, you can use the _dropdown_ element itself and it doesn't feel hacky anymore. That doesn't seem to work in my testing, but was the first thing I tried. Even then, in that example the container itself is set on the `::picker()` pseudoelement, not `div.dropdown`. > Also, consider `@container (width > 30em), (height > 40em)`: `width` and `height` can even query different containers. So it's not clear what this means if the context element was supposed to be "the" container, especially if if only contains in one or zero axes. I'd imagine a `matchSelfAsContainer()` (bikeshed) function would check if the element itself is an established container matching that. So If it has height and width, but only has `container: inline-size`, it would throw. Then, a `matchInsideContainer()` function would check if the element is inside a matching container. I think there's probably need for both. I suspect that anchored container queries would mostly use `matchSelfAsContainer()`, as it is more about state than context, and other queries would mostly use `matchInsideQuery()`. -- GitHub Notification of comment by jamesnw Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6205#issuecomment-4024049447 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 9 March 2026 14:07:45 UTC