- From: weinig via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Feb 2021 19:14:50 +0000
- To: public-css-archive@w3.org
> I'm not quite sure I follow what you're proposing - dropping `auto` or `match`? So presumably _all_ interpolation would default to sRGB unless the author explicitly specified (for example) lch or lab? Yes, I proposing that for gradients (I am not making a point on any other type of interpolation, nor am I proposing we use the existing color-interpolation concept) we keep the current behavior that no specified color space means sRGB, and extend it to allow specifying a specific color space. I am also expressing my opinion that I don't think `match` as a concept is good one, as I don't think it should matter how a color was specified when creating things like gradient. Namely, I think it would be confusing that a gradient specified as: ``` background: linear-gradient(90deg, rgba(255,0,0,1) 0%, rgba(0,0,255,1) 100%); ``` (that is a linear gradient from sRGB red to sRGB blue) would be different that a gradient specified as: ``` background: linear-gradient(90deg, lch(54.29% 106.83 40.85) 0%, lch(29.57% 131.22 301.37) 100%); ``` (that is a linear gradient from sRGB red to sRGB blue, but the input colors use lch() syntax to describe the color) especially given that the input colors can be, and often are, css variables. I think this would lead to confusing behavior as people start to adopt new (to CSS) ways of specifying color like lab(...) and lch(...). -- GitHub Notification of comment by weinig Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5833#issuecomment-786841780 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 26 February 2021 19:14:53 UTC