- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Mon, 14 Jul 2025 22:18:02 +0000
- To: public-css-archive@w3.org
Re: indeterminate and checked/uncheckedness, this was already the case. The CSS :checked and :indeterminate pseudo-classes were *defined* to be mutually exclusive, and browsers obey this, even tho a checkbox can be both `checked=true` and `indeterminate=true` (and thus will submit its value in a form); in this case, it matches :indeterminate but not :checked. The :unchecked language is just following along in this regard. However, I have made it clearer in the spec exactly what the interaction between indeterminate and checked/unchecked should be when they're handled by separate booleans in the host language. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10746#issuecomment-3071200524 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 July 2025 22:18:03 UTC