This makes it possible to have fallback queries for features which are not supported in all browsers, for instance.
Example:
@container --name1 not-supported(--foo: bar), --name2 (width > 600px) {}
Along with the support for multiple queries, the object model is extended to support the 'conditions' attribute on the CSSContainerRule API.Blink component
Blink>CSSWeb Feature ID
container-queriesMotivation
Catching up with the specification and improve interoperability (covered by Interop 2026)
Initial public proposal
No information providedTAG review
No information providedTAG review status
Not applicableGoals for experimentation
NoneRisks
Debuggability
Fixing https://crbug.com/507611251 is necessary to allow editing the full query in the styles pane and will be fixed before enabling this feature. Identifying the matched container element does not support multiple containers, which means for the case below, there will not be a link to the matched container when --unknown is not the query that matches: @container --unknown, --found {} In order to support that, the devtools protocol needs to pass which query in the @container rule that matched.Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
YesYeshttps://wpt.fyi/css/css-conditional/container-queries/at-container-parsing.html https://wpt.fyi/css/css-conditional/container-queries/multiple-style-containers-comma-separated-queries.htmlFlag name on about://flags
enable-experimental-web-platform-featuresFinch feature name
CommaSeparatedContainerQueriesRollout plan
Will ship enabled for all usersRequires code in //chrome?
FalseTracking bug
https://crbug.com/41491726Availability expectation
This is covered by Interop 2026 tests and shipped in Firefox. Expect baseline within 12 months.Estimated milestones
| Shipping on desktop | 150 |
| DevTrial on desktop | 149 |
| Shipping on Android | 150 |
| DevTrial on Android | 149 |
| Shipping on WebView | 150 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
No information providedLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/6196591858941952?gate=4700445638524928
--