[
https://issues.apache.org/jira/browse/WICKET-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117099#comment-13117099
]
Martin Grigorov commented on WICKET-4094:
-----------------------------------------
org.apache.wicket.markup.parser.filter.OpenCloseTagExpander is responsible in
1.5 to fix this problem.
I don't understand what you mean by "validation fails in 1.5".
> "illegal" single-closed textarea tag fails on validation and rendering in
> wicket 1.4.17/18, and succeeds on rendering but not on validation in wicket
> 1.5.0
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-4094
> URL: https://issues.apache.org/jira/browse/WICKET-4094
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.17, 1.4.18, 1.5.0
> Environment: 1.4.17/18 tested on windows with ie and chrome
> 1.5.0 tested on mac and windows with chrome
> Reporter: manuel barzi
> Priority: Minor
> Labels: tag, textarea, wicket
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> continued from http://markmail.org/message/2brq4umaytvswfuv
> supposedly a single closed textarea tag (<textarea.../>) is "illegal", and
> goes against the spec (igor)
> http://www.w3.org/MarkUp/html-spec/html-spec_8.html#SEC8.1.4
> tested on wicket 1.4.17/18. the markup validation does not detect an illegal
> use of textarea, and renders it with both opening and closing tags, but the
> closing tag at the end of the markup, with all the remaining html (after the
> textarea) escaped and included inside textarea contents.
> tested on wicket 1.5.0. the markup validation does not detect an illegal use
> of textarea, and moreover it renders the textarea correctly, with its closing
> tag where corresponds, contrary to wicket 1.4.17/18 behavior.
> so from the point of view of validation, if a single closed textarea tag is
> an "illegal" condition, then both wicket 1.4.17/18 and 1.5.0 fail. but in
> rendering, wicket 1.5.0 works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
