289332 - Back button loads page in wrong frame

Status: RESOLVED DUPLICATE of bug 289323

(Core :: Layout: Images, Video, and HTML Frames, defect)

Description

[jchittu]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050319

This is a unique reproducible case of an earlier bug 28142. Oracle configurator
is one of the Oracle application product and this bug can be reproduced in this
product. 

Oracle configurator is DHTML product heavily uses Javascript and Frames.  We
have 3 top level frames header, content frameset and a invisible frameset
consisting of 2 frames which we call src and proxy. The content frameset will
contain contain max of 2 frames and we call tree and a display frame. The tree
frame display a DHTML tree control and the right side display frame will display
the details of the selected node in the tree. The src frames holds all the
javascript to render dhtml controls on the tree and display frame and also
handles events raised from the tree and display frame. All the events are
handled in src frame and we use proxy frame to post to the server. The server
response comes to proxy frame in the form javascript commands to create and
update controls state.

When running the product in Mozilla 1.7.x, Firefox1.0+ or Netscape7.x we run in
to this bug. Whenever browser back button is pressed the contents from the
display frame is rendered wrongly in src frame.

Reproducible: Always

Steps to Reproduce:
This bug can only be reproduced by running the Oracle configurator DHTML UI. I
could not reproduce this bug in a simpler test case. We are happy to show the
bug through a netmeeting session and we are ready to assist you in all the way
we can to make both Mozilla and our product experience better for our customer.

To reproduce this bug we need to launch configurator DHTML ui and click on tree
nodes to do couple of screen navigation. When i press browser back button the
display frame contents (html page) gets rendered on the src frame. It is
supposed to render on the display frame and not in the src frame window. This
causes our product to loose all application state and any further interaction
leads to javascript error. Since the src and proxy frames are hidden the user
does not know what is happening and it resembles that the client application has
died.

I could not reproduce this bug in a simple test case but i can reproduce this
bug from our product everytime at will.


Actual Results:  
Contents from the display frames gets rendered in the src frame.  

Expected Results:  
This is wrong, contents must get rendered correctly in their own frames when
pressing browser back button

Comment 1

[Matthias Versen [:Matti]]

*** This bug has been marked as a duplicate of 289323 ***