Re: [csswg-drafts] [css-contain] CQ vs shadow boundaries (#5984)

The CSS Working Group just discussed `[css-contain] CQ vs shadow boundaries`, and agreed to the following:

* `RESOLVED: Container queries and units use the flat tree`

<details><summary>The full IRC log of that discussion</summary>
&lt;flackr> emilio: the current behavior of cq and cq units is weird for authors, especially the units. For stuff like style queries, current behavior is using the regular dom which kind of makes sense. But for style queries you really want the flat tree<br>
&lt;miriam> q+<br>
&lt;TabAtkins> q+<br>
&lt;flackr> emilio: we opened this as a result of another issue filed on the units which are right now defined to behave like the queries. The original resolution isn't the best for authors, I think it's a bit weird. miriam thinks so as well and maybe this is worth reverting.<br>
&lt;flackr> emilio: firefox implements what i'm proposing and we haven't run into any issues so i think the compat risk is small<br>
&lt;astearns> ack miriam<br>
&lt;flackr> miriam: I've felt strongly from the start that we went the wrong way. CQ are very much akin to inheritance in a lot of ways and should be treated in that way rather than as selectors in terms of relation to shadow dom. They're all about context and shadow elements and slotting creates context which should be able to be accessed<br>
&lt;astearns> ack TabAtkins<br>
&lt;kizu> q+<br>
&lt;flackr> TabAtkins: ultimately I agree [missed]<br>
&lt;astearns> ack kizu<br>
&lt;flackr> kizu: may be worth mentioning named CQ where we cannot assess a named entity from outside of the shadow dom<br>
&lt;flackr> astearns: any other comments / concerns?<br>
&lt;flackr> emilio: Would be interested in hearing rune's thoughts, can weigh in on issue<br>
&lt;flackr> Proposed resolution: Container queries and units use the flat tree<br>
&lt;flackr> RESOLVED: Container queries and units use the flat tree<br>
&lt;emilio> scribenick: emilio<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5984#issuecomment-2112977366 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 15 May 2024 16:25:05 UTC