User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 If you press Stop while loading an image directly, the half-loaded image disappears and is replaced by the text: The image "filenamehere.jpg" cannot be displayed, because it contains errors. AFAIK all other browsers simply leave the image half-loaded and viewable. This includes Classic Netscape, Firefox's ancestor. And even Firefox leaves half-loaded images visible when Stopping a loading web page. Doing this is preferable since it lets the user take a longer look and/or print if they want. I did this all the time before switching to Firefox, and was annoyed by the "cannot be displayed" message. (Of course it can be displayed, it was just on the screen a second ago!) *If* an error message is still desirable, it can be shown in a yellow Notification Bar without replacing the half-loaded image. Reproducible: Always Steps to Reproduce: 1. Visit the example URL above. 2. Press Stop while the thumbnails are loading. Note that half-loaded thumbnails stop loading, but don't disappear. 3. Click a thumbnail to start loading the full-size image directly. 4. Press Stop before the image can finish loading. Actual Results: The half-loaded image disappears and is replaced by the message: The image "filenamehere.jpg" cannot be displayed, because it contains errors. Expected Results: The half-loaded image stops loading, but remains viewable. Optionally, a yellow Notification Bar appears with the relevant error message. AFAIK all other browsers simply leave the image half-loaded in this situation, without showing an error message.

Dupe of bug 361345?

(In reply to comment #1) > Dupe of bug 361345? > Hmm. I think mine's more general. Though I wouldn't be surprised if my bug were a dupe, since this has ALWAYS been Firefox's behavior, even in the Firebird days. (I forget whether the earlier Mozilla suite behaved this way.) It bugged me even back then, but I didn't think to report it for a few reasons: 1. I had no bug-reporting experience. 2. I assumed it was (dumb) intended behavior, since its ancestor Netscape didn't behave that way. 3. The Notification Bar didn't exist yet, so there wasn't a good alternative for displaying the error without blanking the image. But it finally occurred to me today that the Notification Bar is just the ticket for showing both the picture and the message, if that message is so vital.

why people file bugs in the firebird product if you report something about Gecko (page rendering, Images, networking) instead of core:XXXX and in this case Core:Imagelib ?

(In reply to comment #3) > why people file bugs in the firebird product if you report something about > Gecko (page rendering, Images, networking) instead of core:XXXX and in this > case Core:Imagelib ? The reason's a bit complex, much like the organization of bug categories to the uninitiated ;) Sorry.