W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2016

[csswg-drafts] [css-color] What to do if there's no valid fallback?

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Jul 2016 20:37:49 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-167950631-1469651867-sysbot+gh@w3.org>
tabatkins has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [css-color] What to do if there's no valid fallback? ==
The current spec doesn't define what color to resolve `color()` to 
when all the options cause fallback.  For example, what do you get 
from `color(nonsense-colorspace .1 .2 .3)`?

I think the only two reasonable options are opaque black, or 
transparent black.  Given that the opacity defaults to 100% if 
omitted, I'm leaning toward opaque black.  

On the other hand, we default to "transparent" in similar cases, like 
`image()`, which represents a transparent image with no intrinsic 
dimensions if all the alternatives are invalid, exactly as if you'd 
put `image("nonsense", transparent)`.  This might be explainable by 
the different assumed contexts - most elements don't have background 
images so defaulting to invisible is fine, but most colors are used to
 make things visible so defaulting to an opaque color is better.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/349 using your GitHub 
account
Received on Wednesday, 27 July 2016 20:37:58 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:00 UTC