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

Re: [csswg-drafts] [css-color] What happens in colo() if you pass numbers to a named colorspace, or vice versa?

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Jul 2016 20:43:56 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-235714702-1469652233-sysbot+gh@w3.org>
> I would say for all these type-error, non-matching cases (also one 
where the colorspace identifier has not been declared in an @profile) 
it goes to the next fallback (rather than be discarded, for example).

kk, that works for me.

> It might be an idea to declare that there is an implicit final 
fallback and that the result is transparent black. 

I just opened a separate issue for this.

> Or would that prevent people doing their own fallback for 
non-css-4-color UAs, like:

Can't detect these errors at parse-time anyway, so you have to provide
 your final fallback twice: once in a separate declaration for legacy 
UAs, and once at the end of `color()` for modern UAs.

> btw there is more than one pantone color set, so just the name 
'pantone' is not a good one for examples.

Cool, can you give me a decent example name?  I haven't written any 
named-color examples in the spec yet, but I need to.

GitHub Notification of comment by tabatkins
Please view or discuss this issue at 
using your GitHub account
Received on Wednesday, 27 July 2016 20:44:03 UTC

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