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

> Chrome at some point switched to an HSL-ish form for <input type=color> and its DevTools colorpicker, but in the past used the "triangle and circle" HWB-style picker. I was just watching an artist's stream on Twitch the other day, tho, and whatever drawing program they were using still used triangle-and-circle, too.

A triangle with black at the bottom, white at the top, and the most saturated/high chroma color of a given hue as the third corner is a natural representation of a constant-hue slice through a color gamut. Perceptual representations will have varying shaped triangles (and may have curved edges) while not-really-perceptual ones will go for a regular isosceles triangle.

There are several examples n the spec already, such as 
https://drafts.csswg.org/css-color-4/images/OKLCH-blue-slice.png

Given a constant-hue presentation, there then needs to be a separate means to select the hue and a circle is the natural way to indicate this.

Which is to say that 

1. Triangle-circle representations are common and natural, and
2. They are unrelated to HWB, they apply to any polar colorspace.

> LCH and HSL are identical in terms of ease of creation/manipulation

Not really, and the spec already [makes that very clear](https://drafts.csswg.org/css-color-4/#the-hsl-notation):

> An advantage of HSL over LCH is that, regardless of manipulation, the result always lies inside the sRGB gamut. A disadvantage of HSL over LCH is that hue manipulation changes the visual lightness, and that hues are not evenly spaced apart.

-- 
GitHub Notification of comment by svgeesus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6940#issuecomment-1011170933 using your GitHub account


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

Received on Wednesday, 12 January 2022 15:37:08 UTC