Closed Bug 150004 Opened 24 years ago Closed 23 years ago

Not all pictures are displayed completely

Categories

(Core :: Networking: HTTP, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: damage-list, Assigned: darin.moz)

References

()

Details

When loading the page with Mozilla 1.0 many pictures are not completely displayed. A reload reloads some of the pictures but not all and not only those that were only a part was loaded.
woah, this is not the DOM viewer.
Assignee: alecf → Matti
Component: DOM Viewer → Browser-General
QA Contact: sspitzer → imajes-qa
Reporter: Which connection do you use ?
I use an ISDN (64K) Connection.
-> Darin I saw this with ISDN and i reported a bug but i marked it wfm. Your connection must be busy (page with many big images and/or download in the background) and it depends on the server (AFAIK) i marked my own bug wfm because i couldn't reproduce it later because the original server changed the page (no big images) I can't reproduce it now because i upgraded to DSL :-)
Assignee: Matti → darin
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking: HTTP
Ever confirmed: true
QA Contact: imajes-qa → tever
I have this same problem with most if not all pictures. Usually it appears that there are "stripes" across the picture, sometimes large chunks are just missing. My connecion is LAN/DSL; and other browsers use this connection with no problem P.S. I consider myself relatively computer literate, but this page (all of the bug reporting pages) look like total giberish!
http://grads.iges.org/pix/ea.vort.html Could you test this URL to check if this you see this problem in the page? I can not get all the images displayed even though every image is in the cache according to Page Info. 2002070908 trunk for Mac OS9.x.
WFM linux trunk 2003022108. can anyone reproduce this bug with a more recent build, like mozilla 1.2.1 or mozilla 1.3 beta? thx!
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
I can't reproduce it with Mozilla 1.3 beta, but that can also be because my connection is now a DSL connection with 768kbit/s downstream.
You need to log in before you can comment on or make changes to this bug.