Re: [csswg-drafts] [selectors] Custom state pseudo class proposal (#4805)

The CSS Working Group just discussed `[selectors] Custom state pseudo class proposal`, and agreed to the following:

* `RESOLVED: merge a limited version of https://github.com/WICG/webcomponents/blob/gh-pages/proposals/custom-states-and-state-pseudo-class.md into Selectors 5`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> live*<br>
&lt;emeyer> fantasai: Should we be taking this up and drafting it into Selectors 5, or are we waiting to colelct interest or information?<br>
&lt;emeyer> TabAtkins: Based on our last comment, we’re not super interested in implementing<br>
&lt;emeyer> fantasai: I’ll untag it from mobile 4<br>
&lt;fantasai> s/mobile/selectors/<br>
&lt;emeyer> Rossen: Anyone else interested in taking this up?<br>
&lt;emeyer> TabAtkins: The open question is about to do with non-booleans<br>
&lt;Rossen_> explainer - https://github.com/WICG/webcomponents/blob/gh-pages/proposals/custom-states-and-state-pseudo-class.md<br>
&lt;jarhar> I made a HTML PR here: https://github.com/whatwg/html/pull/8467<br>
&lt;emeyer> TabAtkins: Okay, we actually should take that up. We could merge it into selectors.<br>
&lt;emeyer> fantasai: We should merge it into 5, not 4.<br>
&lt;TabAtkins> https://wicg.github.io/custom-state-pseudo-class/<br>
&lt;emeyer> Rossen: The resolution is we’re going to take the boolean part into selectors 5.<br>
&lt;emeyer> TabAtkins: Joey reminded he has an issue to put this in HTML.  We should mention it in selectors but point over to HTML.<br>
&lt;emeyer> RESOLVED: merge a limited version of https://github.com/WICG/webcomponents/blob/gh-pages/proposals/custom-states-and-state-pseudo-class.md into Selectors 5<br>
&lt;emeyer> github-bot take up https://github.com/w3c/csswg-drafts/issues/6867<br>
</details>


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


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

Received on Wednesday, 30 November 2022 15:23:06 UTC