W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 1998

Re: NOFRAMES (was:Re: Techniques Document)

From: Al Gilman <asgilman@access.digex.net>
Date: Fri, 11 Sep 1998 17:24:40 -0400 (EDT)
Message-Id: <199809112124.RAA00790@access1.digex.net>
To: nir.dagan@econ.upf.es
Cc: w3c-wai-gl@w3.org
to follow up on what nir.dagan@econ.upf.es said:

> Thus spake Al Gilman:
> 
> > If the HTML "document" is designed to occupy a frame in a
> > frameset, and relies on another frame for navbar context, then it
> > would make sense to put a navbar in a NOFRAMES footer section.
> > One might even put header and footer NOFRAMES sections in such an
> > HTML thing.  Header and footer are cropped in the framed
> > presentation, displayed in frame-free presentation.
> 
> Thus I answer:
> The problem is that 
> 1. Most current browsers will show the content of the NOFRAMES element
>    even when the document is "framed"

In this case I would be inclined to humor the existing browser 
population.  I am not sure what the techniques doc. should say
in this case.

> 2. It is not absolutely clear that the implementation as in 1. above 
>    is in contradiction to the HTML4.0 spec.

My reading is that it is a violation.  It takes too much of a
stretch of English to turn "frames are being displayed" to "this
HTML contains a FRAMESET."  "Frames are being displayed" refers
to the state of the browse session, not the contents of the
immediately enclosing HTML element.

But if the industrial consensus is lacking in practice, we should
not put our eggs in that basket.

Al
Received on Friday, 11 September 1998 17:24:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:46:58 GMT