Re: [csswg-drafts] [selectors] Declarative custom `:state()` states (#12502)

> Previously these two conversations seemed to get mixed up - about custom state and custom selectors ([@tabatkins](https://github.com/tabatkins) had a draft started at the end of 2013 - you can still see it at [web.archive.org/web/20140320013932/https://tabatkins.github.io/specs/css-aliases#custom-selectors](https://web.archive.org/web/20140320013932/https://tabatkins.github.io/specs/css-aliases/#custom-selectors))... I'm wondering if it is getting mixed up again, or if it is intentional... Is there a way that you understand headings (in your example) as state (like hover or focus)? I suppose if you squint at it hard enough you could argue the used role is a state, but you can't tell that from selectors really, right? Is it just leaning on old comments that said they were very similar?

Syntactically there is no distinction between state and identity, including in native CSS pseudo-classes (e.g. see #10296). You're understandably thrown a bit by the word "state" which I agree could be more general, but `:state(heading)` works fine by itself, it doesn't _need_ something before the `:` (sorry if I'm stating the obvious, but @westbrook said he hadn't realized before).

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12502#issuecomment-3091274515 using your GitHub account


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

Received on Friday, 18 July 2025 23:54:05 UTC