Re: [community-group] Loosen up the color type (#79)

@romainmenke I know you have, I've appreciated your thoughts in this thread!  To everyone else giving those counter arguments, I appeal to you to _not_ appeal to mediocrity. ;)

> There is no need to add a color space keyword with each hex value if the specification requires that any hex is interpreted as srgb.

So it's defined somewhere!  I'd give consistency bonus points for adding it at all times — encouraging a complete colour-aware standard would be good?  Programs only capable of writing sRGB design tokens can hard code the value.  Technically speaking however, this is good enough for me :)

Apple's system colour picker is notably able to deliver P3 hex codes.

<img width="641" alt="Screenshot 2023-02-07 at 11 25 34 AM" src="https://user-images.githubusercontent.com/5672810/217303598-4681bc0f-449c-4c33-a335-1bd41e9d71cf.png">

> I don't personally agree with this principle but I try to follow it when making suggestions.

Fair enough.  I'd advocate for correctness over convenience of manually typing things in that are wrong?  Add me to the list of people who think bending this rule is okay. 🙃  IMO human readable > easily human writable, especially regarding colour.



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


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

Received on Tuesday, 7 February 2023 16:37:17 UTC