- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Jul 2017 14:42:48 +0000
- To: public-css-archive@w3.org
> Regarding the feedback while writing the gradients sounds plausible. Think of authoring environments like dabblet, codepen, jsfiddle etc, where it's common to have a the result update while typing or browser plugins like LiveReload. Currently one needs to type **a lot** to see a result with gradients and start fiddling with the colors to get them right. > Though a color gradient consists of two or more colors by definition. It also consists of, you know, actual gradation, and yet we support degenerate gradients which consist of 2 solid colors with no gradation between them. > And I fear that if this is introduced, authors may use this one instead of the intended `image(<color>)` function just because they don't know it better or because implementers add the single-color gradient before the `image()` function. And the problem with that is…? If it gives them functionality they need without having to learn more things, I'd say that's a win. If it gives them a feature they need earlier than they might otherwise get it, that's an even bigger win. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1576#issuecomment-313701759 using your GitHub account
Received on Friday, 7 July 2017 14:42:54 UTC