W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment

From: <bugzilla@jessica.w3.org>
Date: Wed, 19 Jan 2011 15:42:04 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PfaAe-0005CI-1c@jessica.w3.org>

Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:

           What    |Removed                     |Added
           Keywords|                            |TrackerRequest

--- Comment #15 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-01-19 15:42:03 UTC ---
I believe I have provided enough info for this bug. Hereby adding

Suggested text for the issue tracker - borrowing a bit from Maciej's

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.

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 Wednesday, 19 January 2011 15:42:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:04 UTC