Virtually all web browsers in use today understand frames, with only one real exception: Lynx, the "text-only" browser, which doesn't even understand pictures. Some few UNIX-based users still like to browse using Lynx because it is very very speedy (since it doesn't download pictures, animations, or other "extraneous" material).
If a web browser which does not understand frames comes to a frame page, a user will see NOTHING. To prevent this, the NOFRAMES tag was created. The NOFRAMES tag provides a shell inside of which an alternate BODY tag may be inserted; this BODY would only be visible to users whose browser is WITHOUT frames capability.
Description: provides a shell to place an alternate BODY tag within, so that users of browsers without frames capability may see something when they come to a frames page. This NOFRAMES tag (which always opens and closes) would be inserted just before the final closing FRAMESET tag of the frame page.
Step One: Insert NOFRAMES tag before closing FRAMESET tag.
<html> <head> <title>Named FRAME Example with NOFRAMES Tag</title> </head> <frameset cols="175,*"> <frame src="./myPage.html" name="nav" /> <frame src="./myOtherPage.html" name="main" /> <noframes> </noframes> </frameset> </html>
Step Two: Add BODY tag with some content inside.
<title>Named FRAME Example with NOFRAMES Tag</title>
<frame src="./myPage.html" name="nav" />
<frame src="./myOtherPage.html" name="main" />
<p>This frame page requires a frames-capable browser, such as Netscape Communicator or Internet Explorer.</p>
In the example above, users WITH frames capability would see the frame page as designed, while users WITHOUT frames capability would see the paragraph of text contained within the BODY tag inside the NOFRAMES tag. Theoretically, you could put as much content as you liked within that alternate BODY tag, but it would be inaccessible and invisible to almost all of your users.
The NOFRAMES tag provides a way of putting a BODY into a frames page for users without frames capability. Today, this is a courtesy mostly for Lynx users, or those rare individuals who still surf using Netscape Navigator 1 or Internet Explorer 1. It is considered good Netiquette to use the NOFRAMES tag, but it is unnecessary to put much content into the alternate BODY tag inside that NOFRAMES tag.
Historically, the NOFRAMES tag was used to provide a completely non-frames version of a web site, which users without frames capability would see; this has become pointless today since almost all browsers understand frames.
Copyright © 2001 Michael Masumoto. All Rights Reserved.