Open Bug 377798 Opened 14 years ago Updated 7 years ago

strange Back button behavior with dynamic frames


(Core :: DOM: Navigation, defect)

Windows XP
Not set





(Reporter: michel.dallaire, Unassigned)




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

Back button becomes available or retain some information when it should not.  So it's misplacing frame content.

Reproducible: Always

Steps to Reproduce:
1. go to  You will have a page with a DIV
2. Click on test1 link at the bottom.  The DIV content will get an iframe and the content of iframe filled with dynamic content of framesets
3. In the upperleft frame, do any search in google.
4. in the bottom right frame, do another search.
5. Click on test2 link at the bottom.  It will change for CNN web site
6. Click on test3 link at the bottom.  It will do the same thing than step 5.
7. Click the Back button.  it was able to reconstruct the older DIV content, iframe and framesets even if it's not the same ID.
8. Now click the tes2 link at the bottom, you will get back to CNN
9. Click the Back button again, the top frame will change to the Google page before your first search.  Now all the frames are mixed up.

Actual Results:  
The frames are mixed up, and I'm able to go back even If the container does not exists anymore.  It recreates some DOM like if it was doing a Back on the JavaScript execution.

Expected Results:  
Back history for that frame disappears since its container does not exists anymore.

From what we tested, in other browsers, (Netscape, Safari, IE6, IE7 and Opera), when a frame is deleted, all it's history goes with it since it does not know where to put it or at least, the Back comes to the page like it was at the beginning with just the DIV but we don't have the frame mixed-up.
Hardware: PC → All
Component: History → History: Session
Product: Firefox → Core
QA Contact: history → history.session
Version: unspecified → Trunk
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
You need to log in before you can comment on or make changes to this bug.