Implement CSSContainerRule.conditions
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Tracking
()
People
(Reporter: emilio, Assigned: emilio)
References
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
| Assignee | ||
Comment 1•4 months ago
|
||
As per https://github.com/w3c/csswg-drafts/pull/13635. To be landed once
there's a resolution and so on.
| Assignee | ||
Comment 2•4 months ago
|
||
Needs tests too of course.
Updated•4 months ago
|
Comment 3•4 months ago
|
||
For quickly making up some tests, I think the cases from the WPT for comma-separated queries could be reused to start.
Updated•4 months ago
|
Updated•4 months ago
|
Comment 6•3 months ago
|
||
| bugherder | ||
Updated•3 months ago
|
Comment 8•3 months ago
|
||
[Why is this notable]: New API replacing existing API
[Affects Firefox for Android]: yes
[Suggested wording]: A new CSSContainerRule.conditions property got introduced holding an array of all container query conditions. This new property is meant to replace CSSContainerRule.containerName and CSSContainerRule.containerQuery, which only supported a single name and query, making them obsolete.
[Links (documentation, blog post, etc)]:
https://groups.google.com/a/mozilla.org/g/dev-platform/c/9NsbuM3nfoI/m/1HWO7dhDAAAJ
This change goes hand in hand with support for multiple comma-separated conditions in @container, which is implemented in bug 2019254. So when that lands, maybe both should be combined in a single release note.
Sebastian
Comment 9•3 months ago
|
||
Added to the Fx151 nightly release notes, please allow 30 minutes for the site to update.
Keeping the relnote-firefox flag as ? to keep it on the radar for inclusion in the final Fx151 release notes.
Updated•2 months ago
|
Comment 11•2 months ago
|
||
FF151 MDN docs work for this tracked in https://github.com/mdn/content/issues/43864 (complete, being reviewed)
Description
•