- From: Dean Jackson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Jul 2016 19:14:29 +0000
- To: public-css-archive@w3.org
I don't have a strong opinion, but I'd like to avoid a situation where we have this: color(adobe-rgb 0.5 0.5 0.5, 0.5) 1. That single comma looks weird, and people will have to remember to use it. Let's avoid a case where people have to think, even for a microsecond, whether they need to add a comma, and punish them if they get it wrong (e.g. gradients) 2. As I commented on twitter, in the vast vast vast majority of these cases, the implementation and the author will know how many color parameters are necessary, and therefore where the alpha is. 3. And in the very very very small set of cases where the implementation doesn't know how many color parameters are necessary, implementations will have to delay processing the parameters anyway. There is no point knowing the alpha before you know the color. And the page author isn't in much danger here - they were the ones who linked to the unusual profile. 4. If the fallback is existing color syntax, then we don't need a separator. It starts with #, rgb or an ident. -- GitHub Notification of comment by grorg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/266#issuecomment-230875020 using your GitHub account
Received on Wednesday, 6 July 2016 19:14:38 UTC