Closed Bug 25450 Opened 25 years ago Closed 25 years ago

Images dont show

Categories

(Core :: Networking, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED DUPLICATE of bug 30267

People

(Reporter: mozilladev, Assigned: pnunn)

References

()

Details

(Whiteboard: [dogfood-][nsbeta2-])

if you go to: WARNING...SEX PAGE! http://teen.sexnation.net/dogfart/gangbang/ The images on this page will not show. Only the alt= text shows. In Netscape 4.7 the images showns just fine.
The alt text is being displayed because the images fail to load. Re-assignig to Networking so they can determine why the images won't load
Assignee: troy → gagan
Component: Layout → Networking
QA Contact: petersen → tever
cc'ing scc.
marking dogfood...
Status: NEW → ASSIGNED
Keywords: dogfood
Summary: Images dont show → [dogfood] Images dont show
... per DP
jud says he won't use mozilla without getting this bug fixed
yea. i said that.
Please give us info on a top 100 site and a technical explanation of what is occuring here. Thanks - pdt.... Putting on pdt- for now.
Whiteboard: [PDT-]
Keywords: beta1
Target Milestone: M14
Since the URL doesn't work anymore the new URL is now: http://teen.sexnation.net/dogfart/weird/ Also SEX site...! Make it work, or Mozilla will never be accepted by the public!!! :)
Putting dogfood in the keyword field.
Summary: [dogfood] Images dont show → Images dont show
New URL: http://teen.sexnation.net/supersex/ Still missing images! build 2000021216
Keywords: beta2
Moving to M15
Target Milestone: M14 → M15
Target Milestone: M15 → M16
I am having this problem, but only on websites running IBMs mainframe s390 webservers. We have identical webpages on different webservers and only the s390 has this problem. This problem surfaced sometime in the last week. Currently using build id 200032909 linux and windows. Here is an internet site that uses the s390 and will demonstrate the problem: http://www.s390.ibm.com/java/
Moving to M17 which is now considered part of beta2.
Target Milestone: M16 → M17
Keywords: nsbeta2
I also experienced 'not showing images' on http://kwark.yi.org/Gfx/jiprood.gif , wich is a generated page that shows http://kwark.yi.org/gfx/jiprood.gif . (notice the case) http://kwark.yi.org/x/gfx.pl/jiprood.gif , wich is the same as http://kwark.yi.org/Gfx/jiprood.gif doesn't have this problem. . This on my underpowered, flaky serial cablemodem connected homemachine, so be patient or try later. (todo: casesensitivetestcase)
Putting on [dogfood-][nsbeta2-] radar. Unless you can give us a top100 site.
Whiteboard: [PDT-] → [dogfood-][nsbeta2-]
I am having this problem with the latest nightly build, 2000060208, on http://www.britannica.com/ It a news/info site by the Encyclopedia Britannica people, and while not a top100, it is a mainstream commercial and very site (and a very good one, too). Needless to say both Communicator 4.73 and IE can display the page fine. Mozilla manages to display 1 image out of 10 or so. For the images not displayed, I see an empty rectangle with the image icon. I can load any of the images by right clicking on it and picking view image.
I'm changing the demo url. I can see the problem on the ibm site and the britannica site. Reassigning to self to see if data stream gets to imglib.
Assignee: gagan → pnunn
Status: ASSIGNED → NEW
The Britannica site is using layers tags. Which could cause the problem. I hate to say it, but layers tags must be implemented by CSS now. Thats what the W3.org decided would be in the standards. I'm still looking at the ibm.com image problem. -p
Status: NEW → ASSIGNED
The image that doesn't display on the ibm site, http://www.s390.ibm.com/java/images/javacol.gif doesn't display with mozilla. If you save the image with 4.7 and save it to a local file, mozilla can display the image easily. -p
The ibm image bug looks like a duplicate of #30267. Marking as a duplicate. *** This bug has been marked as a duplicate of 30267 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
verified DUP
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.