[
https://issues.apache.org/jira/browse/TAP5-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588239#comment-13588239
]
Bob Harner commented on TAP5-2071:
----------------------------------
I like it, but maybe we can do a little better. Rather than passing both
contentType and isHTML5 to markupWriterFactory.newMarkupWriter(...), maybe we
can have the ContentType class itself contain an optional docType property. It
already has a charset property, what's one more? I think this will simplify the
argument lists a bit, although I haven't considered all the implications.
> [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
> Labels: html5, validation
> Attachments: html5.patch
>
>
> 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
