[ 
https://issues.apache.org/jira/browse/TAP5-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tam Du reopened TAP5-697:
-------------------------


I know that OutputRaw component can do that. However, I want to explain my idea.

At first, please consider my example:
I have the string "<Hello>".  I store it in the database. My software will 
filter this string like this "&lt;Hello&gt;" and store it in database.
In .tml file, I have 2 variables ${hello1} and ${hello2}. 
In java file, I have 2 methods 
      getHello1() {...} returns my original string "<Hello>".
      getHello2() {...} returns my stored String in database. Therefore, it 
returns "&lt;Hello&gt;".
I hope that when running this example, it will show string "&lt;Hello&gt;" 2 
times.
But the result is 2 different strings: "&lt;Hello&gt;" and 
"&amp;lt;Hello&amp;gt;".

I agree that it should be always filter the HTML data. But it also should check 
if the HTML data was already filtered. If the data have been filtered already, 
Tapestry should not filter it anymore.


> 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.

Reply via email to