ISSUE-156: Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment

permit-close-tag

Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment

State:
CLOSED
Product:
pre-LC1 HTML 5 spec
Raised by:
Julian Reschke
Opened on:
2011-01-19
Description:
(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 elements 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.

HTML5-SPEC-SECTIONS [void-elements]
Related Actions Items:
No related actions
Related emails:
  1. {minutes} HTML WG telecon 2011-02-24: Action items and Issues (from Paul.Cotton@microsoft.com on 2011-02-24)
  2. {agenda} HTML WG telecon 2011-02-24: Action items and Issues (from Paul.Cotton@microsoft.com on 2011-02-23)
  3. Re: ISSUE-156 permit-close-tag: Chairs Solicit Proposals (from rubys@intertwingly.net on 2011-02-22)
  4. {minutes} HTML WG telecon 2011-02-17: Issues, handling of features, task force reports (from Paul.Cotton@microsoft.com on 2011-02-20)
  5. {agenda} HTML WG telecon 2011-02-17: Issues, handling of features, task force reports (from mjs@apple.com on 2011-02-17)
  6. Re: request to re-open issue 133 due to submission of a change prposal. (from faulkner.steve@gmail.com on 2011-02-01)
  7. {minutes} HTML WG Telecon 2010-01-27: status of actions, new issues, closing items, new calls, charter status (from Paul.Cotton@microsoft.com on 2011-01-27)
  8. {agenda} HTML WG Telecon 2010-01-27: status of actions, new issues, closing items, new calls, charter status (from Paul.Cotton@microsoft.com on 2011-01-26)
  9. ISSUE-156 permit-close-tag: Chairs Solicit Proposals (from rubys@intertwingly.net on 2011-01-20)
  10. RE: {minutes} HTML WG Telecon 2010-01-20: status of actions, calls; task force reports (from adrianba@microsoft.com on 2011-01-20)
  11. HTML-ISSUE-156 (permit-close-tag): Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment ( [HTML 5 spec] (from sysbot+tracker@w3.org on 2011-01-19)

Related notes:

Reverting to raised until a Change Proposal is produced

Sam Ruby, 14 Feb 2011, 15:14:37

http://lists.w3.org/Archives/Public/public-html/2011Feb/0371.html

Sam Ruby, 22 Feb 2011, 19:28:20

Changelog:

Created issue 'Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment (' nickname permit-close-tag owned by Julian Reschke on product HTML 5 spec, description '(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.
' non-public

Julian Reschke, 19 Jan 2011, 17:32:49

Description changed to '(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.

HTML5-SPEC-SECTIONS [void-elements]
'

Julian Reschke, 19 Jan 2011, 22:07:11

title changed to 'Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment'

Julian Reschke, 19 Jan 2011, 22:07:18

Description changed to '(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 elements 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.

HTML5-SPEC-SECTIONS [void-elements]
'

Julian Reschke, 19 Jan 2011, 22:07:42

Product changed to pre-LC1 HTML 5 spec

Sam Ruby, 29 Jan 2011, 18:26:57

Status changed to 'open'

Philippe Le H├ęgaret, 12 Feb 2011, 23:44:14

Status changed to 'raised'

Sam Ruby, 14 Feb 2011, 15:14:37

Status changed to 'closed'

Sam Ruby, 22 Feb 2011, 19:28:19


Paul Cotton <Paul.Cotton@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Sam Ruby <rubys@intertwingly.net>, Chairs, Michael[tm] Smith <mike@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $