- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jul 2016 20:32:49 +0000
- To: public-css-archive@w3.org
tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-color] What happens in colo() if you pass numbers to a named colorspace, or vice versa? == I'm rewriting the `color()` section a bit, and I realized that error-handling for passing the wrong *type* of argument to `color()` isn't defined. That is, what if you write `color(rec2020 "foo")`? Similar cases: `color(pantone .1 .2 .3)` (expects a string, gets numbers), and `color(pantone "foo")` (correctly gets a string, but an unknown value). I think the latter two should maybe fallback? The first one could maybe do that too, but alternately it could just fill in all channels with 0. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/348 using your GitHub account
Received on Wednesday, 27 July 2016 20:32:57 UTC