You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ulrich Stärk (JIRA)" <ji...@apache.org> on 2013/01/14 16:16:13 UTC
[jira] [Commented] (TAP5-773) Select component renderer does not
allow HTML entities
[ https://issues.apache.org/jira/browse/TAP5-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552775#comment-13552775 ]
Ulrich Stärk commented on TAP5-773:
-----------------------------------
Instead of changing it to writeRaw(), which would break behavior in existing apps, I'd add a new parameter to Select and Palette which would default to the current behavior and write out raw if set.
> Select component renderer does not allow HTML entities
> ------------------------------------------------------
>
> Key: TAP5-773
> URL: https://issues.apache.org/jira/browse/TAP5-773
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3.6, 5.2.5, 5.1.0.5
> Reporter: Andy Blower
> Labels: bulk-close-candidate
>
> All ampersands that are returned from getLabel() in an OptionModel get encoded to &. This makes it impossible to use any html entities (— etc) within option labels in selects. This is not that uncommon and should definitely be supported by Tapestry out of the box.
> It can be fixed by changing line 60 of org.apache.tapestry5.internal.util.SelectModelRender from
> writer.write(optionModel.getLabel());
> to
> writer.writeRaw(optionModel.getLabel());
> This would mean that ampersands will need to be encoded for option labels, but this is at least possible for a developer to do. Currently it's not possible to use entities without using a custom select component, you can't even extend the T5 Select class and override the Render nested class.
--
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