@container selectors that contain unsupported queries will never select any containers, meaning they will never match. That means this query will never match any container even if there is a size container that will match the width query that would otherwise make the selector match in cases like this: @container (width > 0px) or (unknown) {} This is a recent change to the specification to avoid forward-compatibility issues.
Compatibiilty risk low as use counter shows a very low instance of unsupported container queries used in Chrome (0.000003%): https://chromestatus.com/metrics/feature/timeline/popularity/4596 There is a much larger risk in not shipping this spec change (which motivated the spec change: https://github.com/w3c/csswg-drafts/issues/7551)
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
https://wpt.fyi/css/css-contain/container-queries/container-selection-unknown-features.html https://wpt.fyi/css/css-contain/container-queries/query-evaluation.html https://wpt.fyi/css/css-contain/container-queries/query-evaluation-style.html
Shipping on desktop | 122 |
DevTrial on desktop | 122 |
Shipping on Android | 122 |
DevTrial on Android | 122 |
Shipping on WebView | 122 |
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).
None