You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/13 17:15:18 UTC

[jira] [Updated] (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:all-tabpanel ]

Jochen Kemnade updated TAP5-773:
--------------------------------

    Labels:   (was: bulk-close-candidate)

> 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
>
> All ampersands that are returned from getLabel() in an OptionModel get encoded to &amp;.  This makes it impossible to use any html entities (&mdash; &nbsp; 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 was sent by Atlassian JIRA
(v6.2#6252)