[
https://issues.apache.org/jira/browse/TAP5-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709816#action_12709816
]
Filip S. Adamsen commented on TAP5-697:
---------------------------------------
Problem is, there's no way for Tapestry to *know* that the data has already
been filtered - if <Hello> was the actual, unfiltered data, this
wouldn't work.
Anyway, just follow Thiago's advice and ust OutputRaw or create a "raw" binding
prefix if it's something you'll need to do a lot. You could even make an
alwaysraw binding prefix to do what you want.
But it's not something that should be changed in Tapestry - that's my €0.02
anyway.
> Tapestry_improvement_ideas
> --------------------------
>
> Key: TAP5-697
> URL: https://issues.apache.org/jira/browse/TAP5-697
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.1.0.5, 5.0.18
> Reporter: Tam Du
> Attachments: DisableHtmlTag.java
>
>
> In the tml file, we should not disable html the second time, that is, if it
> is already disabled, then should not disable again. For more details, I
> attach here my file "DisableHTMLTag.java" which I have been using to not
> disable html the second time. I hope that you can improve this feature in the
> next version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
