235185 - iframe's content is incorrect on reload

Status: RESOLVED DUPLICATE of bug 478273

(SeaMonkey :: General, defect)

Description

[Matthew Walker]

User-Agent:       
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040220

When the src value of an iframe is altered using javascript, the changed value
is kept when even after a document reload.

This problem occurs when the files are on my local filesystem.  When I checked
the problem from my web page Mozilla works correctly.

Reproducible: Always
Steps to Reproduce:
See http://www.massey.ac.nz/~mgwalker/misc/mozilla/main.html
Actual Results:  
The iframe's content displays the wrong page, even though its source value is
correct.

Expected Results:  
The iframe's content should display the page small.html.

Comment 1

[Matthew Walker]

This may be related to bug #148827

Comment 2

[Boris Zbarsky [:bzbarsky]]

Frame state is kept on reload, purposefully.  That way if you click a link in a
frame and then hit reload, the right thing happens (the frame reloads the page
you went to with that click).

Comment 3

[Boris Zbarsky [:bzbarsky]]

*** Bug 354176 has been marked as a duplicate of this bug. ***

Comment 4

[Simon Waters]

Is it possible to have some clarification on how Firefox establishes that the frame it is preserving state for is the same frame as the previous document had?

Seems it is not "id" or "name" or "src", is it merely location in document?

In particular we see this issue arise with "document.location.reload" (not with the browsers reload button which behaves as expected), where the document source has changed the src for the "original" iframe (and one of id or name), but Firefox continues to show the original content, even though we wish this iframe to be distinct from any previous iframe.

Comment 5

[Boris Zbarsky [:bzbarsky]]

> Seems it is not "id" or "name" or "src", is it merely location in document?

Yes.  More precisely, it's effectively the location in window.frames.

Comment 6

[Joel]

I am also having this problem, I've created a new bug describing a very simplistic case to reproduce the issue, since I have no idea how to re-open this bug.

https://bugzilla.mozilla.org/show_bug.cgi?id=478273

Comment 8

[Kevin]

Hey,

Wondering why this ticket is marked as "resolved invalid". This is most definitely a problem that we are running into on a daily basis (Versions 3.5.7 & 3.6). Ticket #356558 has a simple test case.

Any chance on getting this reopened/re-prioritized? It's causing us many headaches.

Comment 9

[Joel]

This ticket has not been resolved as invalid, as basically reports the same issue described above:
https://bugzilla.mozilla.org/show_bug.cgi?id=478273

It is 2 years old and has STILL not been addressed, even in FF 4.