No Frames element

BDoelling@aol.com
Mon, 23 Feb 1998 02:25:41 -0500 (EST)


Date: Mon, 23 Feb 1998 02:25:41 -0500 (EST)
From: BDoelling@aol.com
Message-ID: <f08882e2.34f1246f@aol.com>
To: www-html@w3.org
Subject: No Frames element

The <noframes> element should demonstrate functionality different from the
<body> element, or else it should be eliminated as redundant. At present,
there are three occasions where a <no frames> element would come into play:

1. Browser does not support frames:
	In this instance, <no frames> should be ignored, behaving like a <body> tag.
To my knowledge, this is the current implementation in most browsers.

2. Browser supports frames, but frames are suppressed:
	Once more, <no frames> should function like a <body> tag. Once more, this is
the common implementation.

3. Browser supports frames, frames are not suppressed:
	In this instance, <no frames> should not function as a <body> tag. Browser
should suppress block information between the opening and closing <no frames>
tags. Navigational information that is necessary for frame-suppressed (or
frame-unable) browsing of the page may be included in the <no frames> block.
This is the sort of information that is often redundant in a frame-allowed
page, as it is typically provided inside another frame. A frame-allowed
browser should therefore suppress this infomration. This allows a single
document to work in both a frame-allowed and a frame-unallowed environment,
rather than requiring two complete sets of pages for a site.