- From: Dan V Peterson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Jun 2022 22:30:01 +0000
- To: public-design-tokens-log@w3.org
Very much agreed on wanting support for colors beyond hex values, this is the primary thing that jumped out to me as dangerous when reading the newest proposal. I already use LCH wherever I can in our system's documentation, even though it means more work for me because Figma doesn't support it yet. But it makes it much easier to control perceptual color contrast across a palette, make adjustments to colors while keeping them in the same family, and "lightness" actually means something unlike others where a yellow and a blue with the same lightness or brightness value are so obviously different. Not to mention that it gives us access to so many more colors. Having to set these in hex is incredibly limiting for the future. Whichever format we go with can be converted to whatever format is needed by the tools that use them, without them having to actually support that color space. So shouldn't we try to go with a less limiting structure here so those of us that care to can use something that is easier to understand, supports a wider gamut (than can be restricted where necessary during conversion), and provides additional benefits like easier setup for perceptual color contrast? -- GitHub Notification of comment by danvpeterson Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/137#issuecomment-1157013721 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 22:30:03 UTC