- From: Oliver Williams via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Jul 2022 00:03:33 +0000
- To: public-design-tokens-log@w3.org
Question from @kaelig : > Here's an example use-case, followed by a few questions about the possible flows: > ### Use-case > 1. import a token file > 2. edit a wide-gamut color > 3. save/re-export the token file > > ### Questions > In the context of an sRGB-only tool... > > 1. What should the editing flow/color picking UX be? > 2. When saving/exporting edited color tokens, what sort of prompts would you expect in relation to potential data-loss? > 3. What should the exported data look like (considering the user may have picked an sRGB color, overwriting a P3 color)? 1. If the color's are downgraded to their closest approximation when imported, then color picking would work in Figma/XD/Sketch exactly as it does now. 2/3. I know that the ideal scenario of design tokens is for designers and developers to equally be able to update/change/add tokens, including directly from a design tool, but for teams using modern color, _it's not an advisable workflow yet_. However, if a user does want to overwrite a P3 color with an sRGB color from a design tool, they should be free to do so. The tool should make it clear to the user on initial import that the colors were downgraded with some kind of informational message displaying a list of the names of any affected tokens. I think that is sufficient and does not need to be reiterated on export. @c1rrus I completely agree with everything you have written here, except: > Theoretically the tool could reject the token too, but I think our spec should disallow that. Seeing as simply ignoring values the tool doesn't understand would make it easier for tools to implement, I think they should be given this option in order to aid adoption of the spec. People using modern color realize that it comes with some drawbacks for the time being. -- GitHub Notification of comment by o-t-w Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/157#issuecomment-1176871208 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 July 2022 00:03:35 UTC