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

Re: [csswg-drafts] [css-color] Unnecessary comma in color()

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Jul 2016 17:45:04 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-234025359-1469036701-sysbot+gh@w3.org>
So far my favorite proposal here is `color( [ <colorspace>? <number>+ 
[ / <alpha> ]? ]# )`. I think Brad's suggestion of using commas for 
the fallbacks--and therefore not internally to a color--makes sense. I
 agree that nesting color functions is awkward. There's no reason not 
to just use commas here and indicate rgb or hsl with those 
keywords--it's easier to type, works better when chained, and is 
consistent across all arguments: `color(adobeRGB 0.2 0.6. 0.4 / 100%, 
rgb 0.2 0.67 0.5 / 100%)`

Since we'd also want to allow keywords and #rgb notation, the full 
proposal then would be

```
color(  [ <colorspace>? <number>+ [ / <alpha> ]? ]# [ , <color> ]? )
```

I could go either way on the slash if indeed  only <alpha> can take a 
percentage, but I'm not convinced that's a good restriction to 
introduce for all time.

-- 
GitHub Notification of comment by fantasai
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/266#issuecomment-234025359 
using your GitHub account
Received on Wednesday, 20 July 2016 17:45:11 UTC

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