Closed
Bug 146351
Opened 23 years ago
Closed 23 years ago
image instead of web page rendered
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: c, Assigned: Matti)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.0+)
Gecko/20020522
BuildID: 2002052212
The page should be rendered, instead one image from the page is loaded. I tried
this on RC2 and i downloaded the latest nightly build to make sure. Not sure if
this happens on any other platform.
Reproducible: Always
Steps to Reproduce:
1. go to page
2. look at what's rendered
Actual Results: one image displayed
Expected Results: whole web page (including that image) rendered
It isn't just this page, it happened to me before and i thought it was something
wrong with the site. However i don't remember what page that was. Once i saw
it happened at this page, i knew it wasn't a website thing :) Checked in IE and
it rendered fine. :-\
Reporter | ||
Comment 1•23 years ago
|
||
And yes, i have tried re-starting the browser and (even) the system.
Assignee | ||
Comment 2•23 years ago
|
||
WFm with win2k build 20020521..
Reporter: Have you enabled Http pipelining ?
Can you clear Mozilla Disk Cache ?
Reporter | ||
Comment 3•23 years ago
|
||
pipeline already enabled, clearing the cache & restarting seems to have resolved
it. i guess the question now would be, why would it happen in the first place
and/or why would it allow a single image to be cached for an entire web page?
guess the former is more prudent.
Assignee | ||
Comment 4•23 years ago
|
||
Pipelining is a new Feature and a little bit buggy.
Can you reproduce this without pipelining ?
Or is this now fixed after you cleared the cache ?
If yes: Do you have NS6.x on your system ?
Alex, it could just be that the cache got corrupted for some reason.
Reporter | ||
Comment 6•23 years ago
|
||
could be that too, but how often does the cache get corrupt, i mean it happened
before and i wasn't aware to clear it out.
i was not able to re-produce it once i cleared the cache, the page loaded
properly so this is probably a minor bug. don't know how to be more helpful to
determine its cause.
i had ns 6.x installed on my mac OS system but i erased it once i found how much
nicer mozilla was :) i may or may not have properly uninstalled it. but it
wasn't 'install'ed or running at that time.
do you have any more information about pipelining it? an url or a quick
explaination? my guess would be that it keeps the connection open and requests
multiple documents before closing the connection.
Assignee | ||
Comment 7•23 years ago
|
||
NS6.x can corrupt your disk cache.
Also running 2 instances can corrupt the cache.
Or using a proxy with broken Http/1.1 features (junkbuster....) and Mozilla with
Http/1.1.
Pipelining is a Http/1.1 feature and it should speed up loading on slow-bandwidh
connections. (see the Http/1.1 RFCs)
I mark this wfm because you can't reproduce this.
If you get this again reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•