- From: Matthew Ström via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Dec 2022 17:57:24 +0000
- To: public-design-tokens-log@w3.org
> That would mean that this specification needs to define its own number type completely. I don't see why that's the case, since we're discussing this in the context of spec-defined types like `dimension`, `duration`, etc. I should have been more clear when I said "disallowing scientific notation." Let me rephrase: According to the proposed definition of possible values for `$value`: > 1. A hex code, which is a string that always starts with a # followed by 3,4,6, or 8 alphanumeric characters 0-9,a-f, A-F. > 2. A unitless value, which can be: > a. A string that starts with a non-numeric character and contains any numeric- or non-numeric character afterwards (ie, a string like "bold") > b. A string that starts with numeric characters and contains only numeric characters and/or a single decimal (ie a string that can be cast into a float or int, like "500") >3. A value + unit, which is a string that starts with numeric characters and/or a single decimal, followed by any number of alphabetic characters. (ie "200ms") `123e3px` is not a valid value. `123000px` is the valid equivalent. Do you foresee this causing any problems? -- GitHub Notification of comment by ilikescience Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/121#issuecomment-1344599403 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 December 2022 17:57:26 UTC