Forum Moderators: open
if (parent == self) location.replace("frameset.html");
This script only allows one configuration of pages in the frameset. So, I define a different frameset for each potential orphan. This allows me to create a unique NOFRAMES section for each orphaned content page. There is no conflict between NN and IE here.
If you have lots of potentially orphaned pages and you want to be able to pop each one into the very same frameset using only one script --- well, I'm wrestling with a situation like this right now, and I don't have the answer.
The challenge comes because you can't define a js variable in one window -- the orphaned page, and pass that variable to another window -- the frameset.
Welcome to the forums. Yes, that's another way to accomplish the job.
Advantage: It's backward compatible code, all the way back to JavaScript 1.0
Disadvantage: It makes a second entry to the browser history. The Back button will cause the browser to loop, returning to the same frameset page it started on, instead of what the user expects intuitively.