- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Wed, 29 Dec 2010 22:38:17 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Ian Hickson <ian@hixie.ch>, Norman Walsh <Norman.Walsh@marklogic.com>, public-html@w3.org
Julian Reschke, Wed, 29 Dec 2010 21:24:18 +0100: > On 29.12.2010 20:44, Leif Halvard Silli wrote: ... >>> My proposal is to not allow any new void elements, and thus make >>> parsing and serialization predictable in the future. Also, I think >>> that the new void elements in HTML5 should have been non-void as well. >> >> I actually think we would have come a long way if only >> <newVoid></newVoid> was permitted. It would be logical to allow old >> void elements to be writen as, for example<img></img>, as well - >> perhaps with the exception of</br>. The fact that this is not >> permitted, makes it more difficult to, legally, extend HTML5 with new >> elements. > > Exactly. Bug 8038 [*] - 'Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment' - has still not been resolved. So it is still possible to make that particular chasm narrower, I should think. It needs the bug to be resolved and eventually a change proposal the bug isn't resolved in the right direction. [*] http://www.w3.org/Bugs/Public/show_bug.cgi?id=8038 -- leif halvard silli
Received on Wednesday, 29 December 2010 21:38:52 UTC