[jira] [Commented] (TAP5-2071) Tapestry should output valid HTML5 when using the HTML5 doctype in templates

["Ulrich Stärk (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588267#comment-13588267 ] 

Ulrich Stärk commented on TAP5-2071:
------------------------------------

ContentType is the representation of the MIME content type. The character set is part of a mime content type header (see http://www.ietf.org/rfc/rfc1341.txt, 7.1.1) whereas the doctype is not. While we could abuse it to hold some more information, I'd rather not mess it up. This leaves two options:

An additional DocType type to hold doctype information and pass that to whoever needs it (probably requiring a lot of work to make it truly generic), or a simple marker that fixes the html5 problem at hand. I decided for the latter but I'm ready to review any patches for the first option ;). But then, where and why do we need that information?

Uli
                
> Tapestry should output valid HTML5 when using the HTML5 doctype in templates
> ----------------------------------------------------------------------------
>
>                 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