- From: Miriam Suzanne via GitHub <noreply@w3.org>
- Date: Fri, 13 Jun 2025 16:38:14 +0000
- To: public-css-archive@w3.org
> I don't think this would be needed for ranges. --foo in your ranged example would anyway be "coerced" into a <length> if it indeed contains something that parses as a length. Good point. That is still true in a range like `style(--min < --current < --max)`, right? > Will we ever need to type-ify a literal value without a property to lean on? E.g. `red as <color> => rgb(255, 0, 0)`. I'm not sure I understand when type would be technically necessary. If we can already compare `px` with `rem` and get resolved value comparisons, is there a reason that color names would need to be explicitly typed for a comparison? -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12330#issuecomment-2970920827 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 13 June 2025 16:38:14 UTC