- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Sat, 07 Jan 2023 19:36:42 +0000
- To: public-design-tokens-log@w3.org
Correct that there is no issue with a field supporting multiple types in principle. But the specification doesn't explain or define how to parse this. This is a critical and fundamental issue. It can not be waved away :) If the specification wants to support mixed-type fields it must add a section on how to analyse a value and determine which value it really it is. --- > Technically, we already have this ambiguous definition with the "fontFamily" and "fontWeight" properties That is a bug, not a reason to add more ambiguity :) -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/199#issuecomment-1374586443 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 7 January 2023 19:36:44 UTC