- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 May 2024 15:06:39 +0000
- To: public-design-tokens-log@w3.org
> ```json > { > "left-align-token": { > "$value": { > "web": "start", > "ios": "left", > "android": "left", > "foo": "bar", > "lorem": "ipsum" > } > } > } > ``` While I think this is a very practical solution (thank you!), I’m wary of any solutions that are platform-aware like this. If you have to provide multiple token values based on the platform I think you lose the whole design lift of declaring things once and letting the tool translate it automatically per-platform according to what’s best. This not only inverts the responsibility, it also introduces versioning noise where other platforms are getting version updates when nothing actually changed. I think this illustrates what other comments in this issue have already pointed out—text alignment often may be very dependent on specific localization instances (in many cases localization can even affect the design itself!), and I don’t have any thoughts on whether or not that means this can’t be a token type or not; just agreeing that this _specific_ type has some unique concerns that make it difficult for a simple solution to work. But if there is a good solution, ideally it’s a single value that works automatically for most platforms and most usecases. -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/232#issuecomment-2139850775 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 May 2024 15:06:40 UTC