Over a year ago, Netscape introduced frames as a concept in Web publishing. Frames divide a Web page into separate scrollable windows so that viewers can look at multiple pages simultaneously. Each frame can load information independently of the other frames on the page. Here are ten good reasons to avoid using frames in your MIT Web pages. What you see on screen and what gets printed are usually not the same.
Frames are harder to code, with syntax that includes frameset tags and target windows.
Pages with frames are also harder to maintain. When frames are nested within frames, text can become unreadable. Frames can be coded to open a new, external window. If you want to check the source code of a frame, you have to open at least two documents. An Alternative to Frames Style sheets being developed by the World Wide Web Consortium promise to provide the features of frames in a better implementation.