- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Jul 2017 22:19:31 +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. That means to me that the tools need to be improved to provide some autocompletion. Also, allowing single-color gradients doesn't really save you much, you still have to write a second color to get a proper gradient. You'd just see the first color a little bit earlier. >> 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…? That the semantic between a single-stop gradient is different, so the function will be abused to create color images. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1576#issuecomment-313806320 using your GitHub account
Received on Friday, 7 July 2017 22:19:37 UTC