Update container query WPTs to match recent CSSWG behavior
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox128 | --- | fixed |
People
(Reporter: dshin, Assigned: emilio)
References
(Blocks 1 open bug, )
Details
Attachments
(2 files)
Relevant WPT test here
As per the spec: "Style rules applying to a query container’s shadow-including descendants can be conditioned by querying against it, using the @container conditional group rule. [...] For selectors with pseudo elements, query containers can be established by the shadow-including inclusive ancestors of the ultimate originating element."
We seem to be using flat tree traversal for our container lookup.
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Comment 1•3 years ago
|
||
Seems that the resulting query container can differ within one container query, depending on the inner rules?
| Assignee | ||
Comment 2•3 years ago
|
||
Yeah, this one is one I'm not convinced about, tbh. Seems weird that the spec is using something else than the flat tree (since CSS operates on the flat tree usually). I need to go through the spec issues that made the editors make that decision.
| Reporter | ||
Updated•3 years ago
|
Comment 3•3 years ago
|
||
The severity field is not set for this bug.
:dholbert, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 4•3 years ago
|
||
Marking this S3 for now, pending any further investigation; ni? emilio as a reminder to follow up comment 2.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 6•2 years ago
|
||
As per CSSWG resolution in:
https://github.com/w3c/csswg-drafts/issues/5984#issuecomment-2112977366
Updated•2 years ago
|
Comment 9•2 years ago
|
||
| bugherder | ||
Description
•