Tutorial 14: You've been Framed, Part I
|
| ||||
| ||||
|
|
Providing alternate content for framed documents
Firstly, there is a LONGDESC attribute to the FRAME element that can point to a document providing a description of the frame for those who cannot view frames.
However, if the user is using a browser that does not understand frame syntax at all, then this attribute is useless. This is why we have the NOFRAMES element. The NOFRAMES element may contain anything a BODY element may contain, and is placed inside the top-level FRAMESET element. The contents of this element should be rendered instead of the frameset by browsers that do not display frames, and will (hopefully) be used by browsers who do not understand frame syntax at all, since they will assume its contents to be the contents of a BODY element with implied tags.
The NOFRAMES element
- Context:
- May be placed only inside a FRAMESET element.
- Contents:
- May contain block-level elements.
- Tags:
- Both start-tag and end-tag are required.
Attributes for the NOFRAMES element
- Identifier and classification attributes
- Title attribute
- Inline style information attribute
This means that if you want your document to be compatible with both frame-capable and frame-ignorant browsers, you have to have the same information twice, and in the case of frame-capable browsers, even load it twice, since the frameset document is loaded in its entirety by all browsers, making framed pages even slower to load.
