Another weirdness...
I tested this one on a RH6.2 system:
mozilla-new-cache-opt-nosym-20010314-linux-rh62.tar.gz
Tried to load http://www.digitoday.no/dtno.nsf/wframe/allesaker
Very few of the images actually loaded. I then clicked a link to a story
on the page. That one too had problems finishing loading.
I then hit the back-button:
What had previously been displayed on the first page rendered fairly
quick, then loading of it started again. (The loading of what i assume
was rest of the page, but it never succeeded.)
And here comes the interesting part:
During this loading, each previously rendered image started blinking.
(They are not animated gifs).
All in all each image blinked 5 times. (Vanished/reappeared 5 times.)
This caused a lot of visual annoyance since each "blink" cause all
content on page to jump up and down.
A reload of the page caused the same blinking all over, but all images
still didn't load. A ctrl+reload didn't load all images either.
R.K.Aa.
Darin Fisher wrote:
> Darin Fisher wrote:
>
>> TenThumbs wrote:
>>
>>> It doesn't want to reload them.
>>>
>>> On an SSI document, my Apache server sends just these headers:
>>>
>>> HTTP/1.1 200 OK
>>> Date: Thu, 15 Mar 2001 20:03:44 GMT
>>> Server: Apache/1.3.12 (Unix)
>>> Connection: close
>>> Content-Type: text/html
>>>
>>> There's no Last-Modified or Content-Length header. Reload does
>>> nothing. In
>>> fact, mozilla makes no network connection at all. Shift-reload does
>>> work.
>>> This happens either with a direct connection or via a proxy.
>>>
>> Yeah... this is again the same problem reported above... expiration
>> calc falls apart for simple HTTP responses (ie. those not containing a
>> Last-Modified, Expires, or Cache-Control header).
>>
>> Thanks!
>> Darin
>>
>
> Look for another new-cache enabled linux build to appear on
> ftp.mozilla.org/pub/mozilla/nightly/experimental/ soon. It has a number
> of bug fixes, many of which resulted from the comments posted on this
> newsgroup :-)
>
> Darin