- From: carlosame via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Mar 2021 13:09:38 +0000
- To: public-css-archive@w3.org
> Unless we change the spec We are discussing about changing the spec. In the current spec, the fallback is not a single value but a chain of them: first, a comma-separated list of colors with a specific syntax, then a color with an arbitrary syntax, and finally the opaque black. If the fallback mechanism is removed, it makes sense to ditch that last component as well. > Or with multiple `src` descriptors in `@color-profile` The scenario that I'm considering is a web designer that has/wants to work with an iccMAX profile, and I do not think that he/she is going to 'port' that profile to v4 (which in many cases would be unfeasible) just so people with older/lower-end devices can see the colors. They'd rather go the `lab()` or `lch()` way. And one of the main reasons why people use iccMAX is to have a profile which is based on a reference white different to D50. Imagine a `color()` value with certain color coordinates from a `@color-profile`, and that custom profile having multiple `src` descriptors pointing to profiles based on different whites... A fallback (possibly provided by `var()`) is the proper solution. Let's summarize the use cases for a fallback in a custom-profiled `color()`: 1) The custom profile is iccMAX (or something else in the future), and the device does not support it (this in a world where most mobile devices do not receive OS updates after one or two years). 2) A temporary network failure, due to the site not using a CDN or a CDN issue. 3) Security-conscious government/corporate networks that decide to filter ICC profiles with some rule at the proxy, due to IT security considerations (`@color-profile` rules open a new attack surface to remote attackers). 4) Avoid the 'color glitch' that I described in my previous post. > removing the fallback mechanism makes things cumbersome as an author Another possibility would be to remove custom-profiled colors (which are the only ones that IMHO require a fallback) and the `@color-profile` rule, but that would make people in certain industries not very happy. -- GitHub Notification of comment by carlosame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5931#issuecomment-788897093 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 March 2021 13:09:40 UTC