W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2003

Re: Frames and Accessibility

From: David Woolley <david@djwhome.demon.co.uk>
Date: Sat, 18 Jan 2003 10:38:09 +0000 (GMT)
Message-Id: <200301181038.h0IAc9504143@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org

> Nick, what do you mean "deprecated?" Frameset and frame are not
> deprecated. There appear to be folks on this list that wish they were -
> but not what I read in http://www.w3.org/TR/html401/.  

I think that there is a lot of weasel wording associated with frames
and windowing, but although frames are not actually labelled as 
deprecated, they are in part of the DTD that otherwise differs from
the strict DTD by having all the deprecated features and which authors
were (5 years ago) encouraged to stop using as soon as CSS support
became widespread.  One original argument was that you couldn't deprecate
a feature in the same document in which you first introduced it.  To
me it has all the characteristics of being deprecated, except for actually
be labelled as such.

There is an issue with their not being an XHTL 1.1 Transitional document.
The frames and windows lobby within W3C (from public statements) currently
claims that this doesn't represent the final demise of framing and 
targetting, but rather that the transitional version of XHTML 1.1 would have
been exactly the same as XHTML 1.0 Transitional, so there was no need
to write one.

Note that that lobby is proposing framing and windowing (separate) modules
for XHTML, that are not backwards compatible, but do attempt to address
some of the issues to do with the inability to link to frames pages
other than the initial frameset contents.
Received on Saturday, 18 January 2003 06:48:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:13 UTC