Closed
Bug 205473
Opened 22 years ago
Closed 22 years ago
Reload doesn't refresh
Categories
(Core :: Networking: Cache, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: ok34, Assigned: gordon)
References
()
Details
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4a) Gecko/20030401
The URL above points to a webcam. If you reload this JPEG, Mozilla gets a new
copy of the image from the server (every 30 secods the image is renewed on the
server), but Mozilla does not display it. Hitting reload a second time does not
load a new copy from the server, but displays the image reloaded one step earlier.
Reproducible: Always
Steps to Reproduce:
1.Load URL
2.Wait >30 secs
3.Reload URL
4.Reload again
Actual Results:
After reloading, images does not get refreshed, only after a second click on Reload.
Expected Results:
Refresh the image after it has been fetched again.
Strangely, this does not happen with all webcams. E.g.
http://outstream.camzone.com/camzone-ie?zoo:6:1041624991070:0 does not display
this behaviour. Every reload refreshes.
Both servers generate correct date and time stamp to mark last modification of
the image file.
Reporter | ||
Comment 1•22 years ago
|
||
With Mozilla versions prior to 1.4a this has worked...
Reporter | ||
Comment 2•22 years ago
|
||
The problem is even worse than it looked at first: After reloading images a
couple of times (takes some time) at some random point Mozilla stops displaying
images _at all_. The status line at the bottom of the Mozilla window says
"Stopped" and nothing can make Mozilla reload or display _any_ image at that
point. Even when you switch back to tabs that had already loaded and painted
correctly they are without images. Scrolling these windows magically makes parts
of the images reapper randomly.
Therefore I marked severity "major". And before anyone asks why I don't test
this with 1.4b: 1.4a is the latest version of Mozilla on OS/2.
Severity: normal → major
Comment 3•22 years ago
|
||
This cam seems to be stuck on 05-13-2003 17:46 for the ~10 minutes... no matter
what browser I look at it in.
Reporter | ||
Comment 4•22 years ago
|
||
Well, as it is obviously a European site (TLD .nl) and commercially operated, it
would be logical that it only runs during business hours (CEST).
Checked just now, during business hours, local time.
The time of image on page matches my time : 13.41.
Clicking refresh on 13.42 shows image with time listed as 13.42.
-> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 6•22 years ago
|
||
Sorry no, this bug persists.
I have found that during certain times of the day the bug disappears, only to
reappear soon. Also, in the meantime I have seen that sometimes freshing gives
an older (!) copy of the image. This happens rarely, but I have seen it twice.
Something very weird is going on in the cache, and it's something new. It looks
like something has been changed in the code that checks the last modification
date and time (btw., the bug is independend from the Cache | Compare settings).
I have never seen anything like this on any previous Mozilla build.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Updated•22 years ago
|
Whiteboard: qawanted
Reporter | ||
Comment 7•22 years ago
|
||
With 1.4 beta this issue seems to have been fixed. Every time I click reload a
new image is fetched and immediately painted.
Also, Mozilla no longer says "Stopped" in the status line for every image after
it finished loading, no it says "Done".
So far, the issue of Mozilla losing the ability to paint images after some
prolonged reloading has not surfaced again, so I mark this Bug fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Whiteboard: qawanted
You need to log in
before you can comment on or make changes to this bug.
Description
•