- From: Kathleen McMahon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Nov 2024 22:19:37 +0000
- To: public-design-tokens-log@w3.org
resource11 has just submitted a new pull request for https://github.com/design-tokens/community-group: == Color format adjustments == ## Summary This adds new `$colorSpace`, `colorProfile`, `coordinates`, and `fallback` properties for the color type `$value` object [as suggested by multiple discussions](https://github.com/design-tokens/community-group/issues/137). ## Reasoning This PR takes into account feedback from followup comments with respect to loosening up the color type and gracefully handling legacy color scenarios. ### Pros - What constitutes “color” is somewhat narrow in the spec as-written.The hope is that these additions will empower toolmakers and consumers to leverage modern color spaces, while supporting legacy color profiles depending on display needs. ### Cons - Expanding `$color` in the future would be a breaking change, yet the release of the color format module will already be a breaking change. ## Alternatives - The object syntax (e.g. `$components` / `$channels`) was modified to align with both [CSS Color Module Level 5](https://drafts.csswg.org/css-color-5/#intro) and [ColorJS](https://colorjs.io/docs/spaces) naming conventions for consistency. - This proposal assumes that the `color` module will provide expanded guidance on this format. Or in areas where they potentially overlap, differences will be complementary rather than conflicting. ## Notes - The color first draft PR will be updated depending on feedback here. See https://github.com/design-tokens/community-group/pull/257 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 November 2024 22:19:38 UTC