Re: HTML Frames (enhancement request and SGML declarations)

Earl Hood (ehood@isogen.com)
Mon, 02 Sep 1996 13:04:38 -0500


Message-Id: <199609021804.NAA06911@pow.isogen.com>
To: wtatters@cnrstone.com
cc: www-html@w3.org
Subject: Re: HTML Frames (enhancement request and SGML declarations) 
In-reply-to: Your message of "Mon, 02 Sep 1996 10:10:02 +1000."
             <322A25DA.8EA@cnrstone.com> 
Date: Mon, 02 Sep 1996 13:04:38 -0500
From: Earl Hood <ehood@isogen.com>

> > The noframes element is only for the use of frame-aware browsers.
> > Remember, non-frame aware browsers just ignore the frame markup since
> > they do not recognize it; noframes has no meaning.
> 
> Oops I now see where you are confused.  The NOFRAMES elements IS for use
> with
> non-frame aware browsers !!! !! !!!

Not really, I think your understanding of how NOFRAMES works is
incorrect.  Non-frame browsers do not even know what NOFRAMES means.
The current behavior of HTML browsers is to ignore any tags that are
not recognized.  The NOFRAMES element tells frame-ware browsers what
NOT to render, because they know that non-frame browsers will ignore
all frame related markup and show all markup that is recognized.

This is analgous to when table markup was first introduced.  Browsers
that did not recognize tables just displayed the content since the
unrecognized tags were ignored.  I never saw a non-table aware
browser go: "This is a table, and I cannot render it, so I
better not render it, and/or tell the the user that a table
is here."


> Any HTML code you put inside NOFRAMES tags will be displayed as HTML by
> all browsers EXCEPT those that support frames.  Such browsers will
> instead
> display frame content.

Yep, and I just explained why that works.  Your reasoning behind how
NOFRAMES works was flawed.  When netscape introduced frames, other
browsers did not magically start to recognize the NOFRAMES
element and behave accordingly.  Netscape counted on other browsers
to ignore what was not recognized, and netscape needed a way to
know what markup to ignore when reading a frame specification
document.  Hence, NOFRAMES is for frame-aware browsers since they are
the only ones that recognize the element and its meaning.

If you understand this, you will understand the impacts when new
markup is introduced and how it will affect existing browsers.
Maybe you do understand this, but the wording you choose to use to
explain NOFRAMES implies a functionality of non-frame aware browsers
that is non-existent.

	--ewh