[
https://issues.apache.org/jira/browse/TAP5-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586667#comment-13586667
]
Bob Harner commented on TAP5-2071:
----------------------------------
After just a few minutes of looking through Tapestry's source code, it appears
that Tapestry only has two "markup models" for rendering its HTML/XHTML markup:
1) DefaultMarkupModel -- renders every element having a distinct start and end
tag except for <hr/>, <br/>, <img/>, <link/> and <meta/>.
2) XMLMarkupModel -- renders every element with a distinct start and end tag
For each element (a, input, hr, p, br, etc.), the markup model defines whether
the element uses one of two EndTagStyle variations: "REQUIRE" (always have a
full end tag) and "ABBREVIATE" (use an abbreviated style like <img/>).
I guess what's needed is a third markup model that uses a new, third
EndTagStyle variation, "VOID", for use by those 16 void elements in the HTML5
spec.
> [HTML5 DocType] Remove end tags from all Void Elements (e.g. input)
> -------------------------------------------------------------------
>
> Key: TAP5-2071
> URL: https://issues.apache.org/jira/browse/TAP5-2071
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3.6
> Reporter: Tim Böhler
> Priority: Minor
> Labels: html5, validation
>
> When using a HTML5 DocType in a Tapestry template, the textfield component is
> still rendered with end tags:
> Template:
> <t:textfield t:id="loginEmail" value="loginEmail" type="email" />
> renders as:
> <input id="loginEmail" name="loginEmail" type="email"></input>
> According to the specs, end tags must not be specified for void elements.
> See http://www.w3.org/TR/html5/syntax.html#void-elements
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
