- From: Adam Argyle via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Dec 2020 22:37:15 +0000
- To: public-css-archive@w3.org
The findings shown here are exactly the type of things that powered Una and I to reach out with a request like "can we get some of the basic ones in first, before we solve the entire thing. Most of the usage we've seen in our teams/careers are super basic color manipulations, and designers aren't complaining about the results." We could pacify the majority of users with basic lighten, darken, mix and alpha functions on srgb colors. To me these results look like clear reasons to simplify, but I also really like the direction things are right now. Relative color manipulation, from css and js, looks super rad and I want it, today lol. It's also worth noting from the HTTP Archive results, that most stylesheets did not create robust custom property graphs, and rarely went over 3 nested references. We're all definitely at the tip of the spear when it comes to color manipulation, fidelity and systems. I'd love to make sure my Mom or little brother can use these color functions too, but it's easy to get in the weeds of color space stretching and clamping and distortion. I'm stuck somewhere in the middle of these 2 worlds! Could `hue()` accept a parameter instead of needing to be a separate function for HSL vs LCH? Allow folks to get picky wit-it when they want, but otherwise default them to something expected? -- GitHub Notification of comment by argyleink Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5782#issuecomment-744755405 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 December 2020 22:37:17 UTC