This script solves a problem inherent with frames: when a user calls up a frameset, they are first shown only those pages which the frameset is coded to frame. If the user wants to see a different page in that frameset they will have to navigate to it. For the same reason, a web developer cannot link straight to that second page without either calling it outside of that frameset, leading to major page design problems, or writing a new frameset just to contain that one page.

With this JavaScript I've managed to work around that problem and give developers the power to call any page into one frameset, no matter what page is called for in the frameset's coding. Any user with a JavaScript-disabled browser will get the original frameset and never know the difference. I used this technique in the several sections of ArrowPoint Communication's site, such as the press release section. Even though calling the press releases page (http://www.arrowpoint.com/press_room/releases/index.html) brought up a list of all press releases by default, my JavaScript enables the page to open to any specific press release without creating a new frameset document for each one, such as ArrowPoint's RoadRunner press release (http://www.arrowpoint.com/press_room/releases/index.html?roadrunner.hhtml).

Example
The URL below opens a new window with an example frameset. Note that it opens pages which it is hard coded to call:
http://www.mollerus.net/development/javascript/frameset.htm

Now look at the URL below this paragraph. It calls the same frameset as the previous link, but has another URL appended to it. Note how when the frameset opens, the page in the appended URL is entered into the content frame:
http://www.mollerus.net/development/javascript/
frameset.cfm?/development/javascript/new_content.cfm