- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Oct 2021 17:00:12 +0000
- To: public-css-archive@w3.org
LeaVerou has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-color] Support all existing (non-legacy?) formats in color()? == Yes, I know there are unresolved issues wrt to representing polar coordinates in `color()` and we'd need to solve these first. Maybe by changing its grammar to be `[<number-percentage> | <angle> | none]+` instead of `[<number-percentage> | none]+`. Why should we be able to represent all existing color formats through `color()`? * Right now the distinction between which color formats have a dedicated function and which ones are specified via `color()` is murky. The spec describes `color()` as "Profiled, Device-dependent Colors", but also includes [the XYZ spaces](https://drafts.csswg.org/css-color-4/#valdef-color-xyz) there. * There is no way for authors to parameterize the color space for colors not available in `color()` so that e.g. they can use OKLCH if that's supported or LCH if not. * Even [_we_ are confused](https://github.com/w3c/csswg-drafts/issues/6642#issuecomment-929614506) about whether to add new color spaces in `color()` or as separate functions, imagine how difficult authors will find it to remember the distinction. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6741 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 October 2021 17:00:13 UTC