- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Sat, 30 Jul 2022 15:08:59 +0000
- To: public-css-archive@w3.org
> So, are we comparing these colors before they are converted to the common color space? Right, otherwise all the `none` become `0` > I feel if people are trying to use none to their advantage, it would be best that they work with their colors in a consistent color space to take advantage of the none and avoid none to zero translation. Yes I think we are going to need some authoring guidelines here. We added `none` everywhere (for consistency), when the actual motivation was _powerless hue_; now the spec of course has to say what happens in _all_ cases many of which are far-fetched and are not goig to show up in real-world style sheets. And yes people can use 'none` deliberately, for effect; but then they should be using a starting color space which is perceptually uniform and has semantically meaningful axes (so LCH or OKLCH, basically). > I'm just not sure I personally see much of a benefit to complicating the conversion process for non-alpha components. I can certainly see that point of view. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7536#issuecomment-1200211062 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 30 July 2022 15:09:01 UTC