[WICKET-4094] "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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4.17, 1.4.18, 1.5.0
• Fix Version/s: 1.5.0
• Component/s: wicket
• Labels: tag textarea wicket
• Environment: 1.4.17/18 tested on windows with ie and chrome; 1.5.0 tested on mac and windows with chrome
• Assignee: Igor Vaynberg
• Reporter: manuel barzi
• Created: 29/Sep/11 07:39
• Updated: 29/Sep/11 15:58
• Resolved: 29/Sep/11 15:58

Description

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.