Sounds to me like this is the same issue as image replacement of lazy loading.
https://bugs.webkit.org/show_bug.cgi?id=6656 If you destroy the element, it'll stop loading in a lot of browser, but not webkit. Once requested, it's going to finish downloading no matter what js-foo you throw at it. On Sep 17, 2010, at 4:29 PM, Rolf -nl wrote: > If I am loading an image with asset.image, is it in any way possible > to abort loading when it's running? Like forcing the onabort, doing > the stuff the browser stop button does to images, except that I don't > want to "execute" the stop button (and stop the whole page/window). > > I have this image stack loader class in which I hold an array of > images (the stack) and I load them one after the other like > asset.images, except that I can add an image to the stack with a high/ > mid/low priority setting so it will be the next in line (high prio) > that is loaded. However, if the one that is currently busy loading is > 4mb in size, it still takes a while and it's a waste of bandwidth > really.. so I'd like to cancel/abort that one and run next(). > > I've Googled around, tried some options, but in in the Net/Images tab > in Firebug I keep seeing the progress bar working hard downloading all > these bytes :( > > Any ideas? > > PS > I was thinking loading images with ajax (setting response header > to image/something) so I could cancel the request. But I'm not sure if > that will cache the image correctly or will work at all? >
