LOL, just commented on your StackOverflow version of this question.
Same comment here: Would you quote the URL you use for the image
(leave out the server name if you like) and the headers sent by the
server when the image actually does get downloaded? Perhaps there's an
issue with the expiry headers or something.
Independent Software Consultant
tj / crowder software / com
On May 13, 6:14 am, Josh <joshs.silver...@gmail.com> wrote:
> I have a slide show that creates the next slide dynamically and then
> moves it into view. Since the images are actually sprites, the src is
> transparent.png and the actual image is mapped via background:url(..
> in css.
> Everytime (well, most of the time) the script creates a new element,
> Firefox makes an http request for transparent.png. I have a far-future
> expires header, and Firefox is respecting all other files' expiries.
> Is there a way to avoid these unnecessary requests. Even though the
> server is returning 304 unmodified responses, it would be nice if
> Firefox would respect the expiries on dynamically created images.
> I suspect that if I injected a simple string instead of using new
> Element, this might solve the problem, but I use some methods on the
> Element object, so I would like to avoid a bunch of html strings in my
> js file.
> This is a nit-picky question, but I'm working on front-end
> optimization now, so I thought I would address it.
> You received this message because you are subscribed to the Google Groups
> "Prototype & script.aculo.us" group.
> To post to this group, send email to prototype-scriptacul...@googlegroups.com.
> To unsubscribe from this group, send email to
> For more options, visit this group
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptacul...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at