- From: Christoph Päper via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 May 2017 20:25:02 +0000
- To: public-css-archive@w3.org
The WG resolution conflicts somewhat with [inline issue 9](https://drafts.csswg.org/css-color/#predefined): > Decided at San Francisco to add a larger set of common predefined spaces like AdobeRGB, ProPhoto RGB, and so on. Also coated and uncoated swop, etc, etc. A palette of named (LCH) spot colors may not constitute a color space of its own, but the first parameter to `color()` is not restricted to color space names anyway, even if – as @grorg believes – that was the main reason for this notation. The specification should probably include an informative example of *how* this was possible, i.e. the first example in [11. Profiled, Device-dependent Colors](https://drafts.csswg.org/css-color/#icc-colors) should **include a named color** from an ICC profile. Also, since browsers do not support external ICC profiles – but maybe PDF generators do or will – you cannot “already do this”, which is the very reason for `rec2020` and `image-p3` being predefined. -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/817#issuecomment-304725928 using your GitHub account
Received on Monday, 29 May 2017 20:25:09 UTC