Re: [community-group] High contrast colors (#91)

I definitely agree that platform-specific variance is necessary, and that the way you've outlined to represent them (multiple JSON files) is the right approach.

I think we're puzzling through the use case where you _don't_ want variance (or, want as little variance as possible) when using color keywords. But correct me if I'm misunderstanding.

For example, if you want your text size to be 16px on every platform, that's pretty easy. Whack `16px` in your `tokens.json` level text token, done.

If you want your text color to be the user agent-defined text color is, on every platform?

I agree that `extensions` isn't quite right for this; that seems to be more intended as a place for token authoring tools to keep tool-specific data, not necessarily as hints for compiling code out to end users.

But I also don't think that anchoring the spec on CSS's keywords is quite right; it would also require to the spec to map out the translation between CSS keywords and other platform-specific keywords, lest tools implement their own, inconsistent mappings. It seems in the spirit of the spec to allow for a much more extensible, platform-agnostic way of using color keywords. The `env()` formatting is just one way to do this, there are probably lots. In fact, I imagine that the issue of platform-specific strings (oh no I think we're talking about localization) goes beyond just color, too.


-- 
GitHub Notification of comment by ilikescience
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/91#issuecomment-1011183214 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 12 January 2022 15:48:55 UTC