- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Sun, 21 Mar 2021 03:00:25 +0000
- To: public-css-archive@w3.org
> While testing I frequently turned whole pages black, as my missing profile meant both text _and_ background were black. Frankly anything is an improvement over that. Yup, that is exactly what I was trying to avoid, so I think failing to opaque black is unacceptable in *any* case. Probably the best possible fallback will come from the fallback color space. Note that this could also provide a good fallback while the profile is loading, preventing huge color shifts, which would otherwise deter many authors from using ICC profiles. People could even use it as progressive enhancement. I have also heard there were concerns from the Blink team about having colors that depend on an HTTP request, hopefully this should help alleviate them. However, there is not always a built-in color space that is reasonable, so I don't think we can make this descriptor mandatory. While most ICC profiles are RGB and CMYK, they are not the only ones. This is where IACVT comes in, which, as a last resort, produces far more accessible results than just opaque black everywhere. If we don't want to use IACVT, another option might be to use the property's initial value **if** that is a color, otherwise `transparent`. This prevents the "black text on black background" problem, and doesn't make the entire declaration invalid like IACVT would. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5931#issuecomment-803503729 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 21 March 2021 03:00:27 UTC