Closed Bug 248756 Opened 20 years ago Closed 20 years ago

Transparent GIF images are corrupt at low color depth

Categories

(Core :: Graphics: ImageLib, defect)

PowerPC
macOS
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 239701

People

(Reporter: alex, Assigned: jdunn)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a2) Gecko/20040625
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a2) Gecko/20040625

When I set my display to "thousands" of colors, GIF images with transparent
pixels are corrupted. With "millions" of colors, the problem disappears. The
problem extends to Mozilla's own Alert icon (exclamation mark in yellow triangle.)

Reproducible: Always
Steps to Reproduce:
1. set display to "thousands of colors"
2. type in a bogus url, e.g. "bogus:" in the address bar
3. press "enter" and observe the alert icon.

Actual Results:  
The alert icon comes through grainy and corrupted. 

Expected Results:  
Should have displayed a normal looking alert icon.
WFM / Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a2) Gecko/20040621 +
Nvidia TNT2 @ 800x600x8
Maybe this is video card related and not Mozilla related? I have another TNT2
that showed corrupted alert icons in Windows 98 and it was viodecard BIOS related.
It's probably OS related. I'm running Mac OS X v. 10.2.8 I noticed it first in
Camino 8. There was no such problem in Camino 7, or in Firefox 8 for Mac. I have
a beige G3 with stock ATI video card. But it does show up in the June 25 build
of Mozilla.
I have determined that this bug cropped up in Mozillia 1.7 Beta. (The probem is
absent in 1.7 Alpha.) There is a clue in the 1.7 Beta release notes: "Very wide
images (more than 4095px) will now display on Mac."
(http://mozilla.org/releases/mozilla1.7b/README.html#new)
Known issue.  See duplicate for explanation.

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