[
https://issues.apache.org/jira/browse/TAP5-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAP5-773:
--------------------------------------
Summary: Select component should have parameter to allow option labels to
be rendered w/o HTML entity escaping (was: Select component renderer does not
allow HTML entities)
> Select component should have parameter to allow option labels to be rendered
> w/o HTML entity escaping
> -----------------------------------------------------------------------------------------------------
>
> 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 &. 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 was sent by Atlassian JIRA
(v6.2#6252)
