[
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-test.patch
In the way XmlTag and ComponentTag were changed in WICKET-2829, I thought we
would suggest users to entrust tag attribute escaping to framework. It is not
consistent to decide to escape an attribute or not based in a component flag
designed to model text, and not for tag attribute content.
I'm sending the Sven patch back still failing after r1091299. If suggest user
to entrust tag attribute escaping to framework is not a good idea, I guess we
need a new flag, API and doc explaining that Wicket escapes tag attribute by
default, and you can change this default behavior by setting (...)
> 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: Igor Vaynberg
> Fix For: 1.5-RC4
>
> Attachments: WICKET-3608-test.patch, double_escaped_test.diff,
> wicket-3608.patch
>
>
> 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
