Re: [community-group] Legacy color (#137)

I would also prefer a more future-proof spec that can default/fallback to
hex today while allowing for other color spaces/processes to be used
tomorrow.

 That is what CSS itself is doing in its latest color spec. The move from
v1 which is a trendsetter to the v2 is always chasing the industry ad hoc.
Hence a little bit of foresight goes a long way at least for the skeleton.

On Wed, 15 Jun, 2022, 8:15 pm Nate Baldwin, ***@***.***>
wrote:

> I also don't quite understand nor agree. Hex/sRGB is a fine fallback for
> legacy or small gamut support, and can simply be a required field of the
> token. Display-p3 is already supported by Safari, and used in all retina
> displays. Design tokens capture design data that align with intent. Intent,
> as a designer, is not always to define the lowest common web-friendly
> denominator. Considering the spec already supports fallback notions (an
> array for fontFamily), this decision seems a bit off base.
>
> My position on this is not that the tool chain should support these
> formats. They should, but it's not the design token spec's purpose to
> influence that. Tokens are codification of design decisions, I can't repeat
> that enough. Some people choose fonts that may fail to load on the browser
> (so fallbacks are recommended). Similarly some people choose colors
> tailored for wide gamut displays or based on a specific device-independent
> color space because of relationships between parameters in a perceptually
> uniform space.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/design-tokens/community-group/issues/137#issuecomment-1156567482>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEKS36HQILX4ZZ2SE44BGZDVPHUB5ANCNFSM5YYUJBRA>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>


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


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

Received on Wednesday, 15 June 2022 20:12:14 UTC