W3C home > Mailing lists > Public > public-html-wg-issue-tracking@w3.org > January 2011

HTML-ISSUE-156 (permit-close-tag): Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment ( [HTML 5 spec]

From: HTML Weekly Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 19 Jan 2011 17:32:49 +0000
To: public-html-wg-issue-tracking@w3.org
Message-Id: <E1Pfbtp-00042i-AX@stu.w3.org>

HTML-ISSUE-156 (permit-close-tag): Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment ( [HTML 5 spec]

http://www.w3.org/html/wg/tracker/issues/156

Raised by: Julian Reschke
On product: HTML 5 spec

(raised on behalf of Leif Halvard Silli, see <http://www.w3.org/Bugs/Public/show_bug.cgi?id=8038>):


It is hereby suggested 

* to permit a close tag for new void elements
* to require that the close tag of such eleements would have to
   immediately follow the open tag
   meaning that a close tag separated by content  would have to
   be treated as just a stray close tag and a parse error.  
   Otherwise, if content were permitted and the HTML5-parsers were 
   required to look for the close tag that didn immediately follow, 
   then a  an open tag alone wouldn't work , since the parser then
   would have to parse to the end of the document
    to know if there is a close tag.

This proposal is motivated by two factors: FIRSTLY, to be compatible  with
HTML-parsers that haven't been updated to support a new void, element (and
thereby ease the introduction of new, void, elements) and SECONDLY, by a wish
to align the HTML syntax as much as possible with the XML syntax.
Received on Wednesday, 19 January 2011 17:32:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 19 January 2011 17:32:52 GMT