Main Index |
Top Of Tree |
Tag Index |
Tag History
- What is it?
- This tag is part of the FRAME syntax that allows a regular HTML BODY
structure to be nested in the FRAMESET structure. To older browsers that
do not support the FRAMESET syntax, it appears that the document only
contains the usual <head> and <body> structure [standard HTML behavior is to ignore
tags that are not understood.] Frames capable browsers will ignore NOFRAMES
content.
- Attributes
- This tag accepts no attributes.
- Example
- <html>
<head>
<title>Frames
Example</title>
</head>
<frameset ROWS="20,25%,*">
<frame SRC="frame1.html"
NAME="frame1">
<frame SRC="frame2.html"
NAME="frame2">
<frameset COLS="30%,*">
<frame SRC="frame3.html" NAME="frame3">
<frame SRC="frame4.html" NAME="frame4">
</frameset>
<noframes>
<body>
This text
will appear only if the browser does not support frames.
<body>
</noframes>
</frameset>
</html>
- Parent Model
- <frameset>
- Content Model
- <body>
Tips & Tricks
- I have seen MANY people invoke the NOFRAMES tag incorrectly. Common errors
include using <NOFRAME> or <NO FRAMES>. Browsers generally
do not have a problem with these errors, as anything non-frames related will
be ignored in these cases. Still, it is much better to use the proper syntax.
- It is STRONGLY recommended to include alternate body content
in the NOFRAMES section of a frames definition document. Even if the content
is a link to a non-framed version of the page, this provides users of frames
incapable browsers the chance to view the content of your site.
- DO NOT use the common line in the NOFRAMES element that reads something like:
"You are using a browser
that does not support frames. Go get one here."
- Some users may not want to use browsers that have frames features, or they
simply may not currently have the capacity to use such a browser. If they
wanted such a browser, THEY WOULD ALREADY HAVE IT. Keep
this in mind when designing your pages.
- Technically, it is very likely the NOFRAMES tag serves little purpose
other than to satisy proper syntax and act as a structural nicety.
Browsers that understand frames will not care about anything other
than frame layout statements, and browsers that don't understand frames
will not see the tag anyway. Still - playing nice and using the agreed
syntax is still a very wise idea. =)
Browser Peculiarities
- Anecdote: After the advent of frames, this line started appearing very frequently, and
can still quite frequently be found when searching for information about frames:
"If you can read this, you are
using a frames challenged browser.
This document
has been designed using frames. To view frames
download Netscape Navigator."
This was the message used in the example page at Netscape's site describing
how to use frames.
Boring Copyright Stuff...