For this reason, a server-side scripting language should be deployed for this type functionality. Whether it is ASP, PHP, JSP, ColdFusion or CGI , the scripting language is secondary to the functionality. Developers are free to use the scripting language they are most comfortable with.
Pop-up windows should not be used on Queen's University web pages. They can cause difficulties with novice users for a variety of reasons, and can disorient people that are using screen reading or screen magnification software. In many cases they can also be resource intensive.
Most new browsers and browser add-ons like the Google toolbar, for example, include the ability to block popup windows. To ensure that the content is available to all users, either include the content in a page of its own, or display the content in the original page itself.
Most user agents allow the user to specify if links will open in a new window. It is recommended that the user be in control of how links open in their user agent -- this is the preferred method for dealing with external, off-site links. If new windows are opened, they must be opened with full menus, toolbars, address bars, and status bars available. It must be clearly indicated that the link will open in a new window.
Example: "TheW3C web site provides the definitive HTML specifications: www.w3.org (Note: this will open in a new browser window)"
In the earlier days of the Internet, different web browsers were, to varying degrees, dependent on proprietary code. Web pages, then, were viewed with varying degrees of success depending on the differences between the browser that the site was scripted for and the browser that was being used to view it.
The modern equivalent of browser sniffing is the more robust DOM (Document Object Model) capability sniffing. These techniques will ensure that new browsers require less modification of scripts and less testing.
Moving forward, legacy documents should be reviewed with these scripting issues in mind.