Closed
Bug 46351
Opened 24 years ago
Closed 24 years ago
Reload button does not actually reload, page is persistent
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
People
(Reporter: devotip, Assigned: asa)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m17) Gecko/20000724 BuildID: 2000072408 Using mozilla to display a page being reworked it is not displaing the updates after hitting the reload button Reproducible: Always Steps to Reproduce: 1.have a page on a server (eg http://members/xoom.it/devotip/stub.HTM) 2.open that page and click a link, the link is missing 3.you get a 404 error, it'correct. 4.update the page text, not the wrong links 5.back button, reload button Actual Results: the page is not the updated one Expected Results: the updated page
Hmm i think this bug is invalid: to reaload from cache: click reload to reload from net: click reload WHILE holding in shift-key
Reporter | ||
Comment 2•24 years ago
|
||
IMHO if you hit reload (not counting debug) is because you wish to reload the page from the net. If is ever needed a reload from cache the use of the button and shift button should be exchanged. But again this is my opinion.
well to tell the truth, that's my opinion as well - but i'm just helping out around here as a hobby. The functionality on the reload button is designed to be as described. And that works, in other words?
Reporter | ||
Comment 4•24 years ago
|
||
Yes, I'm too on this just to help. As a bottom line this can become a request to have the reload button behaving as is expected by the people that are going to use the browser but anyway it's not reloading the page even with shift or alt or ctrl. It's stuck on the cache contents.
Assignee | ||
Comment 5•24 years ago
|
||
shift + reload not working right now. this is a dupe of bug 21137 *** This bug has been marked as a duplicate of 21137 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•