- From: Christoph Päper via GitHub <noreply@w3.org>
- Date: Thu, 19 Mar 2026 09:19:14 +0000
- To: public-css-archive@w3.org
I understand that some authors would like keywords match those used in `ValidityState` by HTML DOM, just adjusted to kebab-case. They have been chosen rather inconsistently, though. External compatibility is a sound goal, but I still believe that these should follow a common pattern in Selectors/CSS, e.g.: | Resolution | Variant 1: “mismatch” suffix | Variant 2: qualifier prefix | Variant 3: single word | |---|---|---|---| | `bad-input` | `value-mismatch` | `bad-value`, `bad-input` ✅ | `bad`, `null`, `misentry`, `illformed` | | `custom-error` | `custom-error` ✅ | `custom-requirement` | `custom` | | `pattern-mismatch` | `pattern-mismatch` ✅ | `failed-pattern`, `failed-match` | `malformed`, `mismatch`(`ed`) | | `range-underflow` | `range-underflow` ✅ | `under-range`, `below-range` | (`too-`)`small` | | `range-overflow` | `range-overflow` ✅ | `over-range`, `above-range` | (`too-`)`large` | | `out-of-range` | `range-mismatch` | `outside-range` (✅) | `divergent`, `deviant`, `outlier` | | `step-mismatch` | `step-mismatch` ✅ | `wrong-step` | `misaligned`, `maladjusted`, `irregular` | | `too-long` | `length-overflow` | `over-length`, `above-length` | (`too-`)`long` ✅ | | `too-short` | `length-underflow` | `under-length`, `below-length` | (`too-`)`short` ✅ | | — | `length-mismatch` | `off-length` | `misfit` | | `type-mismatch` | `type-mismatch` ✅ | `wrong-type` | ` incompatible` | | `value-missing` | `value-absent` | `void-value` | `required` | -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1525#issuecomment-4088805813 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 March 2026 09:19:14 UTC