[
https://issues.apache.org/jira/browse/WICKET-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pedro Santos updated WICKET-3608:
---------------------------------
Attachment: WICKET-3608-martinsfix-test.patch
Thanks Attila, I think you solved the puzzle :-)
Sending Martin's patch with a test case.
How about unscape tag attributes in XmlTag.put(key, value) method instead of
the filter solution? IMO it is the correct place and will prevent double
escaping even when user add an escaped value in ComponentTag directly.
> input button escapes escaped value
> ----------------------------------
>
> Key: WICKET-3608
> URL: https://issues.apache.org/jira/browse/WICKET-3608
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Reporter: Sven Meier
> Assignee: Martin Grigorov
> Fix For: 1.5-RC4
>
> Attachments: WICKET-3608-martinsfix-test.patch,
> WICKET-3608-test.patch, WICKET-3608.patch, double_escaped_test.diff
>
>
> An input button with a value attribute containing escaped characters (>)
> is double escaped when rendered. Worked in 1.4.x.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
