[csswg-drafts] [css-color-4] Do we actually need hwb()? (#6940)

LeaVerou has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-color-4] Do we actually need hwb()? ==
`hwb()` was added to CSS Color [over 8 years ago](https://github.com/w3c/csswg-drafts/blame/54f9a867057837f03ad69aae1f16e6d91ae5d394/css-color/Overview.src.html#L994), when we still thought sRGB-only formats and manually tweaking components to create variations were the way to go. The theory was that because its two non-hue components are whiteness and blackness, it would make it easier to create tints and shades of colors.

After going unimplemented for 8 years, it was now implemented in Gecko and WebKit alongside other things in Color 4, but its usage on the web is still 0, so there is no web compat risk in removing it.

Here’s why I think we should remove it:
- We shouldn't be adding new sRGB-only color formats (and even though this has been in the spec for 8+ years, it's new in browsers), instead we should gently guide authors *away* from the existing ones.
- Color modification is now moving in a [different direction](https://drafts.csswg.org/css-color-5) and (OK)Lab/LCH are far superior for creating variations of an existing color and `color-mix()` is far superior for creating tints and shades (mixes with white and black) of any existing color.
- It's not like there's any tooling that uses HWB either so we don't need to keep it around for compat with that.
- It would allow us to close [2 issues](https://github.com/w3c/csswg-drafts/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+hwb+in%3Atitle)

So let's kill it with fire! 🔥🔥🔥 Who's with me? 😃

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6940 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 11 January 2022 12:58:28 UTC