293260 - Should show what it can of a corrupted image

Status: RESOLVED DUPLICATE of bug 150611

(Toolkit :: View Source, defect)

Description

[Steven Augart]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

I think that, in cases where it's really easy to do (for example, here, where
part of the image had already been rendered), Mozilla should show what it can of
a corrupted image, along with a warning that the image is corrupt and cannot be
fully displayed properly.  In this case, I would prefer to have had the
partially-displayed corrupted image on my screen, rather than just the text
message I cite below.

Reproducible: Always

Steps to Reproduce:
1. Visit the above cited URL
Actual Results:  
When I load the above image, I see a lot of it displayed, and then get the message
  -- The image "http://homepage.mac.com/dojothemouse/slash/craniorectal.png"
cannot be displayed, because it contains errors.



Expected Results:  
I think the software should have left the already-rendered part of the image on
the screen, and added a warning that it could not all be displayed because the
image is corrupt.

Comment 1

[Martijn Wargers (dead)]

This could be a duplicate of bug 58880.
I don't get an error message with the url.

Comment 2

[Kevin Brosnan]

WFM - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050507
Firefox/1.0+

Comment 3

[Steven Augart]

This particular image is working for me now also.  

The general problem -- that Firefox should show what it can of a corrupted image
-- remains.  I agree that this isn't the best test case, though.

So, the image will show OK.  Would it make for a better bug report if I manually
corrupt an image and post it on the web or attach it here so that we'll have a
proper test case?  

I sometimes get corrupted web pages and downloads when I use the wireless
networking on my Laptop.  (Intel(R) Pro/Wireless 2200BG, built into an IBM
Thinkpad T42 running MS Windows XP, talking to a Linksys BEFW11S4 V4 Wireless
Cable/DSL Router.)  Unfortunately, Firefox seems pretty insistent about hanging
onto cached web pages, and the only way I've found to convince it to really
reload when I click on Reload is to exit the process and restart Firefox.)

Comment 4

[Matthias Versen [:Matti]]

This is no Firefox bug, it's core/Imagelib and it's a dupe.


*** This bug has been marked as a duplicate of 150611 ***