Previously Martin Aspeli wrote: > Wichert Akkerman wrote: > >Previously Malthe Borch wrote: > >>Reinout van Rees wrote: > >>>From a caching viewpoint, I normally end up putting &dtml-portal_url; > >>>everywhere into the css files to make sure all the images and so are > >>>loaded from one place and not 20 times from /img.jpg, > >>>/subfolder/img.jpg, /sub/sub/img.jpg and so on. > >>This really isn't necessary; images referenced from a stylesheet are > >>local to the url that contains the stylesheet. > > > >The URLs for our stylesheets are dynamic. > > Are you sure? They're dynamic, but they only change if you re-save the > portal_css configuration. If the caching proxy or the browser has cached > an image at /portal_css/<random>/img.jpg then that's going to be stable, > I think, until you re-save portal_css.
I don't think it is desirable to reload all images for a CSS change. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
