[ 
https://issues.apache.org/jira/browse/WICKET-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941811#comment-13941811
 ] 

Martin Grigorov commented on WICKET-5242:
-----------------------------------------

<html>
        <head>
                <script>
                                function showDetailedMsg(msg) {
                                        console.log("MSG: " + msg);
                                }
                </script
        </head>

        <body>
                        <a wicket:id="status" href="#" id="ok" 
onclick="showDetailedMsg(&#039;This is a detailed message&#039;); return 
false">ERROR</a>
        </body>
</html>


is a valid HTML that works fine. Clicking on the link writes "MSG: This is a 
detailed message" to the console.

> Disable escaping of html tag attributes
> ---------------------------------------
>
>                 Key: WICKET-5242
>                 URL: https://issues.apache.org/jira/browse/WICKET-5242
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 6.7.0
>            Reporter: Bertrand Guay-Paquet
>              Labels: escaping, html, tags
>
> Currently, all component tag attributes are escaped.With html5 data- 
> attributes, much more values can be considered valid depending on the tag 
> attribute and some should not be escaped.
> For example, bootstrap tooltips use the "data-title" attribute to set the 
> content of a tooltip. Using Wicket's tag attributes, it's not possible to set 
> the value "<b>hello world</b>" as the data-title since it is escaped.
> ComponentTag#writeOutput() is the method which calls 
> Strings.escapeMarkup(value); and escapes tag values. This is called by 
> Component#renderComponentTag().
> There should be a way to disable component tag escaping either per-tag or 
> per-component.
> Reference email thread:
> http://apache-wicket.1842946.n4.nabble.com/AttributeModifier-with-html-in-the-attribute-tp4659206.html



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to