W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2020

Re: [csswg-drafts] "Can't be displayed" is undefined (#5046)

From: Chris Lilley via GitHub <sysbot+gh@w3.org>
Date: Thu, 17 Sep 2020 13:23:59 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-694230174-1600349038-sysbot+gh@w3.org>
> That suggests we might want to limit ourselves to the "color-space not yet loaded" case, and leave gamut-handling to something else (addressed below). That simplifies the fallback logic significantly, as well.

It was a concern over tying **out-of-output-device-gamut** in as part of **cannot-be-displayed** that led to @LeaVerou and I discussing this yesterday (and her write-up of the issues we discussed).

My edits today and yesterday have been adding the out of gamut stuff, to see how it looks. But I am certainly open to splitting the two concepts again and handling them differently.

I want it to be possible for an author to specify a preferred fallback to a given color; I also want good things to happen if the author does not do that.

GitHub Notification of comment by svgeesus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5046#issuecomment-694230174 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 September 2020 13:24:01 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:16 UTC