Calculating colors within CSS as part of a build step or on the fly is more a niche usecase though, so I'm a bit sceptic if lch capability within CSS would have a big effect on design tools considering the existing options mentioned above.
The main usecase is for design, from where you'd export hex values for development for most dev usecases.
LCH collides with Adobes own color system they use for Kuler/Adobe color, which is a proprietary perception based system. Pantone of course, it also rivals their proprietary system (they sell expensive color swatch books to designers), and NCS, another proprietary perception based system that is mostly used in interior design. Strong forces within the industry with an self preserving interest.
So the hopes are more on rivaling tools like Figma and Sketch to implement LCH. With LCH they could even do print, because process colors can be easily derived from those..
Most monitors that... Macs have? As a Windows/Linux user, none of the monitors I've used as my daily driver are wide-gamut. The only wide-gamut monitor I've really seen was in my university's computer lab. It displayed every color a bit more brightly, and my laptop didn't desaturate colors to compensate.
> Firefox does not implement the spec that restricts CSS colors to sRGB. Instead, it just throws the raw RGB coordinates on the screen, so e.g. rgb(100% 0% 0%) is the brightest red your screen can display. While this may seem like a superior solution, it’s incredibly inconsistent: specifying a color is approximate at best, since every screen displays it differently. By restricting CSS colors to a known color space (sRGB) we gained device independence. LCH and Lab are also device independent as they are based on actual measured color.
Yeah that explains why.