Closed Bug 436 Opened 26 years ago Closed 26 years ago

Doesn't display some GIFs

Categories

(Core :: Graphics: ImageLib, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: rob, Assigned: pnunn)

References

()

Details

(Whiteboard: Holding verification until new app shell is available.)

Created by   (rob@gadgetguru.com) on Tuesday, June 9, 1998 2:40:25 PM PDT
Additional Details :
Check out http://www.gadgetguru.com/ - on the menu on the
left hand side, the very top and bottom GIFs show the
"broken image" icon, everything else displays correctly.
It can't seem to find those two images, even though they
display properly in other browsers. This has been present
since the first source release. I'm currently using today's
(06/08/98) build.
Updated by   (rob@gadgetguru.com) on Wednesday, June 10, 1998 11:14:04 AM PDT
Additional Details :
Additional investigation shows that Mozilla is having a problem with the
redirections given by Apache's mod_speling module. The graphic mtop.gif was
incorrectly referenced on the page as MTop.gif, mod_speling attempted to correct
the error and redirect to the correct image, but Mozilla didn't take the
redirection.
Status: NEW → ASSIGNED
I just checked this page with todays build and
the images are displaying fine. Are you still having
trouble viewing this page?
-thanks
pnunn
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Nope, it seems to be working fine now. Must have been fixed somewhere along the
line.
QA Contact: 1698
Eli -- please verify bug
Whiteboard: Holding verification until new app shell is available.
Per pnunn, holding verification until new app shell is available.
Bulk moving Mozilla/ImageLig bugs to NGLayout/Image in preparation for a move to
Browser/ImageLib.
Status: RESOLVED → VERIFIED
Using the 3.16.99 Apprunner builds (Win32, Mac OS & Linux), I'm also not seeing
this problem anymore.

Thus, marking as verified.

(Rob, please re-open with your comments if you're seeing this recurring; thanks!)
You need to log in before you can comment on or make changes to this bug.