[css-conditional-5] "query-less" container query support
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox149 | --- | fixed |
People
(Reporter: afrehner.work, Assigned: afrehner.work)
References
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
Steps to reproduce:
The spec supports the idea of "query-less" / "no query" container queries. To clarify:
https://drafts.csswg.org/css-conditional-5/#container-rule
outlines it as
<container-condition> = [ <container-name>? <container-query>? ]!
<container-name> = <custom-ident>
<container-query> = not <query-in-parens>
| <query-in-parens> [ [ and <query-in-parens> ]* | [ or <query-in-parens> ]* ]
where <container-query> is now optional. This enables queries like
@container --name {}
to work, and the goal is to simply apply the styles if it is inside a container with that name --name.
WPTs exist here https://github.com/web-platform-tests/wpt/blob/master/css/css-conditional/container-queries/query-container-name.html
I'd like to implement this in Firefox so that it's all wrapped up https://wpt.fyi/results/css/css-conditional/container-queries/query-container-name.html?label=experimental&label=master&aligned
Actual results:
"query-less" container queries don't work
Expected results:
they should work.
Comment 1•2 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::CSS Parsing and Computation' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Assignee | ||
Comment 2•2 months ago
|
||
Updated•2 months ago
|
Backed out for causing wpt failures
Comment 6•2 months ago
|
||
Ah, you need to annotate the extra passes. Please do that and we can get that re-landed. Thanks!
Comment 9•2 months ago
|
||
| bugherder | ||
Updated•2 months ago
|
Updated•2 months ago
|
Comment 10•1 month ago
•
|
||
FF149 MDN work for this can be tracked in https://github.com/mdn/content/issues/43212
Does this reflect a recent spec change?
I'm trying this on browserstack and the https://wpt.live/css/css-conditional/container-queries/query-container-name.html test fails on the most recent versions of all browsers they have. Looking at https://wpt.fyi/results/css/css-conditional/container-queries/query-container-name.html?label=master&label=experimental&aligned the versions are more recent, so it could be simply I don't have the right versions to test. Note, it does work locally on nightly.
The reason I ask is that I presume I will need to update the compatibility data, and it is useful to know when each browser updated.
Updated•1 month ago
|
| Assignee | ||
Comment 11•1 month ago
|
||
Does this reflect a recent spec change?
Not very recent https://github.com/w3c/csswg-drafts/issues/9192#issuecomment-1789850349 , but recently implemented in browsers.
Webkit: in STP release 235 https://webkit.org/blog/17739/release-notes-for-safari-technology-preview-235/
I don't have insight into Firefox's nor Chrome's release timelines, but as you noted it's been implemented in both, so just waiting on releases.
| Assignee | ||
Comment 12•1 month ago
|
||
Sorry, spec changed here specifically https://github.com/w3c/csswg-drafts/pull/11172
Updated•1 month ago
|
Description
•