- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 26 Aug 2009 11:37:13 -0500
- To: François REMY <fremycompany_pub@yahoo.fr>
- Cc: David Perrell <davidp@hpaa.com>, www-style list <www-style@w3.org>
On Wed, Aug 26, 2009 at 11:24 AM, François REMY<fremycompany_pub@yahoo.fr> wrote: > From: "David Perrell" <davidp@hpaa.com> >> >> Should there be a means to name (and cache) a gradient 'generated image' >> for >> reuse? If I have a class that uses the same gradient throughout a website, >> might it not be counter-productive, relative to a cached image file, to >> have >> the gradient reconstructed at each occurance? > > Caching may be useful, but it's the browser that should take the decision of > performing > or not caching based on the type of gradient. That kind of consideration > should not be > left in the hands of the web designer. > > Many factors may enter in the decision of caching : > * Specificity of a gradient (could a cached image of the gradient be used > whichever size the box has, or not) > * Time needed to paint the gradient > * Available memory to cache the gradient > * ... > > The web designer could never perform good decisions since they don't have > many keys of the equation in their hands. > > (It's my meaning, at least) This is also basically the same issue that exists around using data: uris for images in CSS. They're not currently cached, but they could potentially be. ~TJ
Received on Wednesday, 26 August 2009 16:38:17 UTC