- From: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>
- Date: Sat, 04 Feb 2012 04:14:05 +0400
- To: Lea Verou <leaverou@gmail.com>
- Cc: www-style@w3.org,Hugh Guiney <hugh.guiney@gmail.com>,whatwg <whatwg@whatwg.org>
04.02.2012, 04:12, "Lea Verou" <leaverou@gmail.com>: > 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) DIVs are disallowed as direct children of lists due to purely theoretical limitation while in practice they work.
Received on Saturday, 4 February 2012 00:14:42 UTC