- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Oct 2021 11:45:53 +0000
- To: public-css-archive@w3.org
svgeesus has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-color-4] Is the fallback for `device-cmyk()` needed == The [`color()` function](https://drafts.csswg.org/css-color-4/Overview.html#color-function) used to have a fallback, which added significant complication to implementation, bulked up the object model, without adding much value, and was dropped. The [`device-cmyk()` function](https://drafts.csswg.org/css-color-4/Overview.html#device-cmyk) still as the same style of fallback. Is this needed? The same arguments against the `color()` fallback apply here. On the other hand I'm aware the primary use is CSS to PDF converters (which typically do not construct object models) and maybe they rely on having a fallback? What do the proprietary cmyk extensions in various PDF generators use, do they have a fallback or do they depend on the usual CSS falback mechanisms? Note that now that the preferred way to implement `device-cmyk()` is to associate t with an ICC profile, so generating an RGB preview for example is much more tractable than it used to be. Unless there is significant feedback in favor of keeping the fallback, I propose to remove it. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6721 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 October 2021 11:45:55 UTC