- From: Nate Baldwin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Jun 2022 14:45:30 +0000
- To: public-design-tokens-log@w3.org
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. -- GitHub Notification of comment by NateBaldwinDesign Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/137#issuecomment-1156567482 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 14:45:32 UTC