- From: Dan Burzo via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Oct 2021 18:54:22 +0000
- To: public-css-archive@w3.org
A few thoughts on @tabatkins's additions: > For all other purposes, a missing component behaves as a zero value, in the appropriate unit for that component: 0, 0%, or 0deg. This includes rendering the color directly, converting it to another color space, etc. Is it worth it to have `alpha` behave differently with `none = 1`? It feels like _transparent_ is a bad default for, let's say, `hsl(45deg 50% 50% / none)`. Having it behave like the solid color `hsl(45deg 50% 50%)` makes it more useful in mixed-usage scenarios, where the same color value is both rendered and interpolated. > It can also be specified explicitly, by providing the keyword none for a component in a color function. All color functions allow any of their components to be specified as none. I assume this includes the `color()` syntax as well, right? > Also, I don't think device-cmyk() ever has powerless components, right? Even if k is 100%, the other three components can still have an effect on making it black "warm" or "cool", right? Yes, see [Rich black](https://en.wikipedia.org/wiki/Rich_black). -- GitHub Notification of comment by danburzo Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6107#issuecomment-932803366 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 2 October 2021 18:54:24 UTC