W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: <di>? Please?

From: Lea Verou <leaverou@gmail.com>
Date: Sat, 04 Feb 2012 02:12:26 +0200
Message-ID: <4F2C77EA.2030703@gmail.com>
To: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>
CC: www-style@w3.org, Hugh Guiney <hugh.guiney@gmail.com>, whatwg <whatwg@whatwg.org>
On 4/2/12 01:38, Marat Tanalin | tanalin.com wrote:
> 04.02.2012, 03:29, "Lea Verou"<leaverou@gmail.com>:
>> On 4/2/12 00:38, Marat Tanalin | tanalin.com wrote:
>>
>>>   The problem is that it will most likely not be solved via CSS (solved means we have finished CR spec and all browsers supports it) in near 10 years or so, while DIV wrapper work _right now_ in all browsers.
>>
>> The same could be said for anything that currently has some kind of
>> workaround:
>> - Lets not spec variables, we have find&  replace.
>> - Lets not spec new layout models, we have floats.
>> - Lets not spec css3-conditional, we have Modernizr.
>> ...
>>
>> --
>> Lea Verou (http://lea.verou.me | @LeaVerou)
>
> The analogies are wrong. We are free to spec anything, but it's not a reason to disallow something that already work in favor of something that does not exist yet.
>
> Correct analogies:
> * disallow floats just because new layout models are in development;
> * disallow using Modernizr since we have unimplemented css3-conditional draft;
> * disallow using find&replace since we have a draft for spec variables.

Huh? Who said divs are going to be disallowed?!

-- 
Lea Verou (http://lea.verou.me | @LeaVerou)
Received on Saturday, 4 February 2012 00:12:59 GMT

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