- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Dec 2023 21:29:14 +0000
- To: public-css-archive@w3.org
I'm curious if the fact that the CSS selector spec *used* to say this but now doesn't was an intentional or unintentional change to the selector spec. From a usage perspective this change seems weird -- I think conceptually `:indeterminate` was intended to act like a third state that is distinct from `:checked` and unchecked. Even though it wasn't defined that way in the DOM, that doesn't mean it's desirable to expose the DOM weirdness about it in *more* places. Also cc @tantek who I think was (at least partly) responsible for creating indeterminate. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9706#issuecomment-1854728430 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 December 2023 21:29:16 UTC