230321 - Incorrect cache page loaded when using HTML frames, JavaScript location.replace() and browser Back button

Status: RESOLVED EXPIRED

(Core :: DOM: Navigation, defect)

Description

[Jason K Carter]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007

If you have two HTML frames, where the first calls the
document.location.replace() JavaScript function on the second, and then you
follow a link on the second frame, and then click the "Back" button, the
incorrect cache page is loaded in the second frame.  It's easier to just use the
example page to understand the problem:

http://maizecoop.cropsci.uiuc.edu/bugzilla2/

Reproducible: Always

Steps to Reproduce:
1.Load http://maizecoop.cropsci.uiuc.edu/bugzilla2/
2.Click the first button in the left HTML frame to load "Page 1".
3.Click the "Back" browser button
4.Click the second button in the left HTML frame to load "Page 2".
5.Click the HTML link in the right HTML frame.
6.Click the "Back" browser button.

Actual Results:  
"Page 1" was loaded from the cache.

Expected Results:  
"Page 2" should have been loaded from the cache.

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

sounds more like session history than cache

Comment 2

[Jose Fandos]

Confirming with Mozilla 1.7 final in Windows XP. location.replace adds to the
history. It shouldn't. RPC calls using the method described in
http://developer.apple.com/internet/webcontent/iframe.html suffer from history
being modified with the links loaded in via location.replace.

Owner feel free to confirm and change status to New.

Comment 3

[Jason K Carter]

Is anyone going to work on this bug?

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.