- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Jan 2023 22:41:15 +0000
- To: public-css-archive@w3.org
Agenda+ to discuss with the working group. The tradeoffs are: 1. **Limit the set of color spaces more**. This avoids 'unnecessary' options, without locking us into 'intent' names where a better space-for-the-intent might come along in the future. However, the set is somewhat arbitrary-seeming, and the intents are not clear by the name of the space. Authors have to memorize or look up the best option in each case. 2. **Allow any color space**. Some of them are redundant, or not particularly useful - but at least we're not making an arbitrary choice, when all of them have meaningful behavior. This seems to be the developing not-quite-consensus, but it's not excellent. Maybe the arbitrary limitation forces authors to consider more carefully? 3. **Declarative names based on author intent**. In terms of code legibility, learning, and teaching - this seems like an obvious choice. But as soon as we define the best color space for a given intent, we are likely locked into that choice for the future. If a more perceptually-uniform option comes along, we have no clear way to update our options. I don't love these options - but I'd like to see this addressed one way or the other before the feature ships. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7907#issuecomment-1377989911 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 January 2023 22:41:17 UTC