In a nutshell it never completed in Safari (I'm sorry, I can't remember which version I am running at work). If the image existed in the browser cache before the script was called, then the script was able to access it, but it never actually reported that it was complete.
Has anyone else run into anything similar?
Shall I dig up some juicy details?
I'm sort of hoping there is some obscure bug like the very lame case issue that I recently ran into with IE and dynamic image maps when experimenting with a kludgy, circular, rotating, thingamajigg. Enough said!
border: The value of the border attribute in HTML name: The name attribute of the img tag complete: A property that is true if the image has finished loading (read-only - you cannot change this attribute) height: The height of the image (in pixers -/ returned as an integer) width: The width of the image (in pixels - returned as an integer) hspace: The horizontal space around the image vspace: The vertical space around the image lowsrc: The image preview as defined in the attribute of the same name src: The URL of the image
Since Christian Heilmann is a big fan of standard DOM features and does a very good job of describing how to use them well (he also does a great job of explaining how it used to be done, and why that isn't necessarily a great idea anymore)... and because he didn't issue any caveats about the image properties, I sort of assumed that these were standard.
And we all know what happens when we assume!
The list at w3.org doesn't have complete and lowsrc, but does have additional properties: - align - alt - isMap - useMap - longDesc
There are actually a lot of non-standard properties that are in general use, and are supported across browsers because they are popular (innerHTML, for example). Apparently, Image.complete isn't one of them.
Does the onload property of the image elements not work for you? [ May 24, 2008: Message edited by: Bear Bibeault ]