- From: Matt Ström-Awn via GitHub <noreply@w3.org>
- Date: Mon, 15 Dec 2025 17:48:42 +0000
- To: public-design-tokens-log@w3.org
I appreciate this proposal! It's very well-articulated. Here's some feedback: 1. My hypothesis is that having _some_ types with shorthands, but other types without, could create some confusion. 2. Separating out units and values was done for a few reasons ([see original thread](https://github.com/design-tokens/community-group/issues/121)); one of the main ones was parser simplicity/precision. Bringing in unitless values here increases parser complexity. 3. I don't believe this is actually backwards-compatible — a tool that follows the 2025.10 spec would consider the unitless token invalid; so introducing this syntax would be a breaking change. Given the above, I'd recommend against adopting the proposal as-is. -- GitHub Notification of comment by ilikescience Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/342#issuecomment-3656880372 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 December 2025 17:48:43 UTC