- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Mar 2020 09:53:57 +0000
- To: public-css-archive@w3.org
The new examples are great, even though I'm not entirely sold on the double hyphens. Yes, the syntax makes it a bit more complex, but it's easy enough to carve out an exception for device-cmyk if required. I'm no longer sure that it is. My only real concern is this requirement to use the "naive algorithm" for rendering. It will result in authors avoiding device-cmyk, because it looks awful when previewed in a browser. With two years of hindsight on this issue, I think simply allowing browsers to choose an arbitrary profile for device-cmyk, instead of being forced to use the naive algorithm, is the best solution. Yes, it will make the results vary from browser to browser - that's what you'd expect from device-dependent CMYK. Allowing an author to "redefine" device-cmyk to another space is less important - they can, of course, just use the `color()` function if they care that much about it. -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2022#issuecomment-600525908 using your GitHub account
Received on Wednesday, 18 March 2020 09:53:59 UTC