- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Mar 2021 13:31:59 +0000
- To: public-css-archive@w3.org
>> Unless we change the spec > We are discussing about changing the spec. Yes :) @tabatkins was pointing out that if that change were made, another change would also need to be made to have the intended result. > If the fallback mechanism is removed, it makes sense to ditch that last component as well. That would make the result undefined, which seems worse than "defined, but not what you want" i.e. opaque black. > 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. Fair point, although many of the things that you can do in iccMax you can't do with just a single `lab()` value, for example: - spectral processing - BDRF - material appearance modelling - custom observer functions - most things using the calc element > one of the main reasons why people use iccMAX is to have a profile which is based on a reference white different to D50. In my (admittedly limited, but certainly non-zero) experience of what people use iccMAX for, that is a nice-to-have but also the easiest to get an ICC v.4 fallback ad certainly not the main reason iccMAX is being used today. > 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. Yes, that would basically make it useless for any use case where an enumerated list of predefined colorspace is insufficient. It would be like removing images, videos and webfonts from the platform, because sometimes they don't load. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5931#issuecomment-788910964 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:32:01 UTC