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

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

From: Axel Dahmen <brille1@hotmail.com>
Date: Thu, 1 Apr 2010 12:59:21 +0200
To: www-style@w3.org
Message-ID: <hp1uae$587$1@dough.gmane.org>
I see. But how about the lost abilities presented by a frameset?

CSS could provide means to re-gain the plus points gained by frames.

I particularly think of the ability to split two adjacent block-elements.

I suggest to create of a property allowing a group of two adjacent 
inline-block or block elements to be resizable without the need of 
JavaScript.




----------------------------
"Tab Atkins Jr." <jackalmage@gmail.com> schrieb im Newsbeitrag 
news:dd0fbad1003300719i579acaa2td8a91926701ee01f@mail.gmail.com...
> On Tue, Mar 30, 2010 at 3:42 AM, Axel Dahmen <brille1@hotmail.com> wrote:
>> Hmm, it seems this discussion stalls now...
>>
>> HTML5 apparently has deprecated frames without providing or looking for 
>> the
>> existence of appropriate alternatives.
>>
>> So what is the CSS group going to do? Do we accept regression? Or do we 
>> want
>> to set up new rules to enlarge the richness of CSS/HTML?
>
> Personally?  We accept regression.  The HTML5 change isn't new.
> Framesets were discouraged as far back as HTML4 (which is why there
> was a special DOCTYPE just for it, so they could restrict them from
> the main Transitional and Strict DOCTYPEs).  There are very good
> reasons for them being disallowed, which we've talked about before,
> and very little reason to continue using them.  It is not worth the
> time or effort of this group to attempt to do anything further with
> them.
>
> ~TJ
>
> 
Received on Thursday, 1 April 2010 11:00:08 GMT

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