- From: Sebastian Friedrich via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Jun 2022 18:52:39 +0000
- To: public-design-tokens-log@w3.org
Fully agree @o-t-w , I don't use wide gamut color but have my thoughts sorted on how I would want to have it. For the ones who aren't convinced here: What Chrome and other browsers implement there right now dates back 90 years from now to color theory research about human perception. Also design systems are not meant to cover a subset of what CSS can help one to build, it is the other way around. It is also worth noting, that a design system shall help manage media breaks more reliability than without such a system in place. Delegating color conversion, which shall be assumed lossy by default, to a random tool at sort of runtime is accepting that applying color via tokens will have different and unforseeable deviations. CieLCh or similar might be a good start for thinking. Ultimately I would hope for the ability to describe any custom color space by an 3x3 conversion matrix and for better usability hard code the most common ones as named presets to use out-of-the-box. The work of Bruce Lindbloom might be a good read to get into the math of the topic: http://www.brucelindbloom.com/ -- GitHub Notification of comment by sebfriedrich Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/137#issuecomment-1155599950 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 June 2022 18:52:41 UTC