Re: [csswg-drafts] [css-contain-3] Container Queries and pseudo elements (#6711)

The CSS Working Group just discussed `[css-contain-3] Container Queries and pseudo elements`, and agreed to the following:

* `RESOLVED: Accept proposal to in all cases use originating element`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-contain-3] Container Queries and pseudo elements<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/6711<br>
&lt;dael> rune: I wanted to take issues 4 &amp; 6 at same time. Hvae prop for both<br>
&lt;dael> rune: Easy to explain for psuedo elements. When on selectors the originating element is closest query container<br>
&lt;dael> rune: Spec currently doesn't say anything about pseudo elements<br>
&lt;dael> rune: For issue with shadow dom prop is establish query container as the shadow including and having the originating element of the select be the first one poss to query<br>
&lt;dael> rune: Prop is in the shadow dom issue for that<br>
&lt;dael> rune: There's the explaination for how this fits with slotted, before, after, etc<br>
&lt;miriam> this comment: https://github.com/w3c/csswg-drafts/issues/5984#issuecomment-980694443<br>
&lt;dael> rune: TabAtkins do you have a better way to explain?<br>
&lt;dael> TabAtkins: All in all 3 cases to worry about. first is ordinary tree abiding before and after. That's simple, originating element. Act like they're children already<br>
&lt;Rossen_> s/rune/futhark/<br>
&lt;Rossen_> q?<br>
&lt;dael> TabAtkins: 2nd is shadow dom like ::part. Refers to element in shadow, but originates in host. If there are query containers between them will they be seen? We believe no b/c would expose internal details of the shadow.<br>
&lt;dael> TabAtkins: If users want to query on the dom they see, they won't get that<br>
&lt;dael> TabAtkins: Again use originating element<br>
&lt;dael> TabAtkins: Final is non-tree like first-line and first-letter.<br>
&lt;dael> TabAtkins: Example where div for first-letter is used. Actual markup is a &lt;p> that's a query container. I think again this is not seen b/c otherwise exposes where in the tree the non-abiding pseudo is. We've keep them away from answering for various reasons<br>
&lt;dael> TabAtkins: By saying for purpose of query containers we use the originating element and skip the &lt;p> it's nice and simple<br>
&lt;dael> TabAtkins: IN all cases use originating element. Straightforward and easy to understand<br>
&lt;dael> fantasai: I think proposal makes sense.<br>
&lt;dael> futhark: one thing not sure about is multiple pseudo. What's the originating. div before marker. Is the originating of the marker before?<br>
&lt;dael> futhark: Attempted to spec final originating element<br>
&lt;dael> fantasai: Yes. Term is ultimate originating element<br>
&lt;dael> TabAtkins: And agree that's what we want to use<br>
&lt;dael> Rossen_: Hearing agreement<br>
&lt;dael> Rossen_: Anything we're missing here? Other opinions?<br>
&lt;dael> Rossen_: Obj to accept this proposal?<br>
&lt;dael> RESOLVED: Accept proposal to in all cases use originating element<br>
</details>


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


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

Received on Thursday, 3 February 2022 00:31:33 UTC