- From: Matthew Ström via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Jan 2022 21:57:10 +0000
- To: public-design-tokens-log@w3.org
One possibility is to take the lead from CSS and allow for a user-agent-defined value through something like `env()`. In this case, you might define a stack of possible user agent values, with a static value as a fallback. Like this:
```json
{
"color": {
"highlight": {
"type": "color",
"value": "env(Highlight, SystemColorHighlightColor, #00ffff)",
}
}
}
```
Kind of like how font stacks work: the parser would evaluate the list from right to left, returning the first match it finds in the user agent. So in a browser, that'd get interpreted as using the UA Highlight color, in WinUI it gets the value of SystemColorHighlightColor, and anywhere those things don't exist it just ends up being #00ffff.
--
GitHub Notification of comment by ilikescience
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/91#issuecomment-1010394511 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 January 2022 21:57:11 UTC