- From: L. David Baron <dbaron@fas.harvard.edu>
- Date: Thu, 18 Feb 1999 16:47:24 -0500 (EST)
- To: www-html@w3.org
Tim Bagot <tsb@earth.li> wrote: >Of course, frames are now deprecated, and not supported by CSS, which >provides similar functionality through other mechanisms. A combination of CSS and OBJECT inclusion of other html documents (or use of DIVs if one wants to duplicate content in many files) can be used to do something like this. For example, the fixed part of the frameset (the contents / toolbar frame) can be in a separate file, and included in the files that change (so that the URLs change) by using OBJECT. One could set the OBJECT (or DIV) and a DIV containing the main contents to have position: fixed and scroll: auto (and the correct position). I don't think, however, that this would work in any current browser. However, this does not handle what I see as one of the best features of frames. They can be resized by the user. I don't think I will stop using frames until this can be done another (reliable) way. (I also see the saving of bandwidth as an important feature.) It would be nice if there were some URL syntax that could store the state of a frameset. This would solve the main problem frames cause. I think there was talk of this a few years ago (when frames first appeared), but certainly nothing ever came out of it. David Baron ----------------------------------------------------------------- L. David Baron Freshman, Harvard dbaron@fas.harvard.edu Links, SatPix, CSS, etc. < http://www.fas.harvard.edu/~dbaron/ > WSP CSS AC < http://www.webstandards.org/css/ >
Received on Thursday, 18 February 1999 16:47:27 UTC