Closed Bug 287373 Opened 19 years ago Closed 19 years ago

PNG looks wrong, presumably a decoding error


(Core :: Graphics: ImageLib, defect)

Not set





(Reporter: mark, Assigned: pavlov)





(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050210 Firefox/1.0 (Debian package 1.0+dfsg.1-6)
Build Identifier: Firefox 1.0.1

A user of Mac OS X 10.3.4, Firefox 1.0.1 tells me that looks wrong to him in Firefox, although
that PNG looks fine with other Mac image viewers. I don't have a Mac, but it
also looks fine to me from Windows and Linux.

Reproducible: Always

Steps to Reproduce:
Start up Firefox 1.0.1 on Mac OS X 10.3.4. Take a look at

To see how it should look, look at that PNG with something else.
Actual Results:  
The image looked "corrupted"

Expected Results:  
The software should have rendered the image just like other viewers of it do.

The bug was reported to me by Chris Ball, copied on this report. He is cjb at
mrao dot cam dot ac dot uk.
The user could have a corrupted image in browser cache.
Try Shift + Reload on the image.

If that doesn't fix it, please attach a screenshot of the rendering.
Maybe bug 239701
Apparently, Shift-Reload doesn't solve the problem. I got the user to send me a
screenshot - as you can see, he sent one for
which uses the same logo.png graphic. (He reports that the problem is the same
when he looks at just the png.)

I also asked him for the User Agent string for his browser. It's Mozilla/5.0
(Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050225
Does the problem go away in a nightly build? Does it only occur with colors set
to thousands in system prefs?
(In reply to comment #4)
> Does the problem go away in a nightly build? Does it only occur with colors set
> to thousands in system prefs?

Good catch -- it does indeed only occur with colours set to thousands.  I can't
test with the disk image of yesterday's nightly build, since it launches and
then disappears from my process list immediately, even when run with
-ProfileManager.  That'll have to be a separate bug.  :)

- Chris.
So what does "wrong" or "corrupted" mean here?  Is the image just being dithered
because of the limited color space?
This looks like one of our old QuickDraw bugs. The reporter should try a recent
nightly trunk build.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:

*** This bug has been marked as a duplicate of 239701 ***
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.