Sounds DOM related. => Vidur.
It is not that JS needs to cache images, it's that we need an image cache. Then when JS goes to get an image it comes from the cache, but this is transparent to JS. I am assigning this over to fur as an additional test case for the image cache or he can mark it as a duplicate.
First, it's not clear what the bug is since there's no description of the problem in the report. Second, the network memory cache has nothing to do with the image cache. Assigning to pnunn...
rods: There is an image cache. It was never disabled. Currently the reload policy on all images (except animated gifs) is set to get the image from the cache if it exists in the cache. If not, get it from the server. Animated gifs get the image from the netlib cache for every loop. Since this cache doesn't exist yet, the image is retrieved from the server. I'm closing this as invalid, unless someone can further clarify the problem. -pn
I'm reopening this one. Just because the analysis of the problem is incorrect doesn't mean there isn't a problem with js images. -pn
Clearing INVALID resolution due to reopen.
Sounds like a dup of 13325.
I agree. It does sound like a dupe. -p *** This bug has been marked as a duplicate of 13325 ***
verified duplicate of 13325