Closed Bug 58602 Opened 25 years ago Closed 24 years ago

location.replace(url) must be called twice before page will load again

Categories

(Core :: DOM: Core & HTML, defect, P3)

x86
Windows 2000
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: wcd, Assigned: jst)

Details

MULTI-FRAME ENVIRONMENT... I have a scripted page which is effectively "self modifying" through a call to a function in the base frame. This function uses document.write to create part of the page content on the fly ... the vast majority of the page is just plain HTML 4.01. If a function is called that attempts to reload the window with the document from the same URL using location.replace(url) the first call results in the document in the frame scrolling to the top of the page as if it were locally refreshed from the cache. The second call has the desired effect - the page completely reloads and generates new content based on variables that have been set in the base frame by other user actions. A 'NASTY' workaround is to append a dynamically constructed query string based on the current time to the url. i.e. location.replace(url) ... requires two goes. location.replace(url + "?" + myTime) works every time, albiet at the expense of reloading the entire page from the web-server each time it is called. IE45 and NS4 do not have this problem; ANY call to location.replace(url) will replace the page from the contents of the cache.
Assignee: asa → jst
Component: Browser-General → DOM Level 0
QA Contact: doronr → desale
Over to DOM
We need a testcase that shows this problem in order to look into possible sollutions, could you attach a testcase to this bug? Thanks!
OK - Will take a bit of time to construct a simple test case due to need to construct a frameset. I will put this on my list of things to do before the end of the week.
Is anyone still seeing this problem?
Marking INVALID due to lack of Response. Reopen if this is still a problem.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.