- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Aug 2011 10:39:43 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13128 --- Comment #9 from Marat Tanalin <mtanalin@yandex.ru> 2011-08-14 10:39:43 UTC --- (In reply to comment #8) > If the only reason is styling, then we should fix this in CSS. You are free to fix this in CSS (be it in 10 or 20 years), but, until this is fixed in CSS, this should be possible with currently available features. DIV insides lists are actually supported in browsers and should be just documented into spec. This is not something new, so nothing to be rejected. This is only formal validation issue. > Furthermore, this massively complicates the processing that tools would have to > do to process lists. Right now it's very simple, you get the element and you > walk its children. If we make the markup at this level arbitrarily complicated, > it's going to cause all kinds of troubles. I don't think so. Purely formal restriction is not something that helps web-developer who want that this restriction to not exist. This would be logical inconsistence. > Another reason is that it's syntactically dangerous. Can you spot the mistake > here? > > <ul> > <li>... > <li>... > <div> > <li>... > <li>... > </div> > <li>... > </ul> If list items have closing tags (they always do as for good web-developer), then there is no errors here. Again: current browsers already DO support wrapping list items in DIV, there is nothing to reject here, this should be just document into spec as actual current behavior of all current browsers. Thanks. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 14 August 2011 10:39:48 UTC