- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Mar 2025 22:44:58 +0000
- To: public-css-archive@w3.org
This function isn't doing parsing on a value; it shouldn't take a `<syntax>` argument. The form control *knows* what type of value it contains - a string, a number, a color, etc. It should just take a handful of keywords (probably just `number`, `percentage`, `color`, `string`?), and go IACVT if you request a type that the form control doesn't support. * All controls would support `string`, resolving to the same string value you get from the `.value` property. * `number` and `range` inputs support `number`. * Progress/meter support `number` and `percentage` (with the default ranges being 0-1 and 0%-100%) * Color inputs support `color`. * Maybe `file` inputs can support an `image` keyword? There's many complaints thru the years of not being able to easily do "upload previews" on the web (tho today you can wrangle it with blob: urls) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11842#issuecomment-2705107420 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 March 2025 22:44:59 UTC