W3C home > Mailing lists > Public > www-html@w3.org > July 2000

Re: Frames

From: Rupert Wood <rup@kanat.pair.com>
Date: Tue, 4 Jul 2000 08:43:34 -0400 (EDT)
To: www-html@w3.org
Message-ID: <Pine.BSF.4.10.10007040825450.6680-100000@kanat.pair.com>
On Tue, 4 Jul 2000, Dave J Woolley wrote:

> > doesn't include any frame element. Does it mean that frames are
> > not recommended or being phased out? If so, what problems do
> > frames cause?
> It means that they have never been in any reccommended version.

So what's the status of frameset.dtd? I understood that frames had not
been deprecated but rather just removed from the strict DTD: frameset
documents should not contain bodies, nor should documents with bodies
contain framesets - hence they must use a separate DTD.

> Frames result in unbookmarkable pages, framing in other sites
> (often considered a copyright violation), deep links that
> don't work well (sometimes they work worse because of
> Javascript to force the frameset back in++

Yeah, but these are points of style and subjective.

Frames can work well, and there are some circumstances where they are
necessary as well as desirable; notably combined client and server-side
applications use frames (often hidden) to store code and preserve state.
Granted these do shed a little backwards compatibility over pure
server-side solutions, but use much smaller downloads per operation,
with all the associated benefits.

Rup.
Received on Tuesday, 4 July 2000 08:43:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:43 GMT