W3C home > Mailing lists > Public > www-style@w3.org > March 2010

Re: Frameset/Frame Specification Amendment (HTML+CSS)

From: Patrick Garies <pgaries@fastmail.us>
Date: Sat, 27 Mar 2010 05:16:55 -0500
Message-ID: <4BADDB17.2060109@fastmail.us>
To: Andrew Fedoniouk <news@terrainformatica.com>
CC: Axel Dahmen <brille1@hotmail.com>, www-style@w3.org
On 2010-03-26 10:54 PM, Andrew Fedoniouk wrote:
> Yes, <frame>s have their own use cases and benefits.
> Notable example (at least for me) is http://www.rsdn.ru - forum engine
> that is quite bandwidth and battery efficient.
> Other examples are help systems that have index/content layout, etc.

Separating content from navigation without a good reason is a bad idea; 
if you want a faster rendering, XSLT would probably be a better choice 
since you explicitly tie the navigation and content together and don't 
break bookmarking. It also means that you aren't forced to fix part of 
the layout of your document where you wasting screen real-estate when 
the user wants to scroll (unless you allow resizing, but, in practice, 
most authors turn it off). This also sidesteps the styling issue that 
Axel brought up since you don't have to deal with the incompatibilities 
in styling frames.

As for good uses, I can't come up with anything that iframes, in 
conjunction with CSS, can't already do.
Received on Saturday, 27 March 2010 10:17:33 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:25 GMT