443667 - Back does not work properly with frames

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Wesley Ribeiro]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

In a page with two frames, I change the page displayed on frame B by submitting a form on frame A, and then click on a link on this new page on frame B to go to another page (which will now be on frame B). If I click the Back button now, frame B will show the initial page, instead of the previous one.

Reproducible: Always

Steps to Reproduce:
1. Initial page with two frames. Frame A has a form which, when submitted, will change the page on Frame B. Frame B initially displays page 1.html
2. I submit the form on Frame A, so Frame B will now display page 2.html
3. I click on a link on the page on Frame B. This will make Frame B display page 3.html
4. I press the Back button on the browser. 
Actual Results:  
Instead of going back to display page 2.html (which was FF 2 behavior), Frame B now displays page 1.html.

Expected Results:  
Frame B should display page 2.html

If I use the Back option on the right-button mouse menu, the problem does not occur.

Comment 1

[Wesley Ribeiro]

Attachment: Minimal test case to show the problem

Comment 2

[Tyler Downer [He/Him]]

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

Comment 3

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.