Re: [csswg-drafts] [selectors] Pseudo-class to indicate when a slot has content (#6867)

The CSS Working Group just discussed `[selectors] Pseudo-class to indicate when a slot has content`, and agreed to the following:

* `ACTION: keithamus to open issue about ::slotted() cascade order`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> Rossen9: who's best to summarize this one?<br>
&lt;emilio> dbaron: was discussed yesterday according to github-bot<br>
&lt;dbaron> https://github.com/w3c/csswg-drafts/issues/6867#issuecomment-2378207271<br>
&lt;emilio> keithamus: didn't resolve because I had a question about the functional pseudo-class<br>
&lt;emilio> ... to do the same things I was talking about<br>
&lt;emilio> ... wrt /slotted/<br>
&lt;emilio> ... I think we need to pick a direction, either we look into the slotted combinator or we look into :has-slotted()<br>
&lt;emilio> q+<br>
&lt;dandclark> emilio: Did we resolve on the nonfunctional version?<br>
&lt;emilio> keithamus: we resolved to that prior<br>
&lt;emilio> ... but test were written for the functional pseudo-class<br>
&lt;Rossen9> ack emilio<br>
&lt;emilio> ... it seems the functional pseudo is more interesting to the WC community<br>
&lt;emilio> ... but happy to investigate the combinator<br>
&lt;emilio> emilio: Given :has-slotted() is dependent on whether we do the combinator, and the combinator kinda depends on what we do about the cascade order, I'd prefer to discuss the cascade order at least first, when TabAtkins is around ideally<br>
&lt;dandclark> emilio: We can keep the tests as tentative or I can split it<br>
&lt;dandclark> emilio: I think we need an issue about the cascade issue<br>
&lt;dandclark> ...wasn't clear that was the main complaint about the slotted selector<br>
&lt;emilio> ACTION: keithamus to open issue about ::slotted() cascade order<br>
</details>


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


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

Received on Saturday, 28 September 2024 00:12:18 UTC