html tags in node text

[Becky]

I have two websites, both .net 4, both using telerik dll 2012.215.1.40, and they do not render treeview nodes with html tags the same way. See attached files - "goodtree" is the desired behavior. I added a plain unordered list in "badtree" for comparison to see if all of my code was affected (something web.config or app pool related), but it is only the treeview. I am stumped. How can I get "badtree" to render the html instead of printing out the tags?

[Bozhidar]

Hello Becky,

Please go to the following forum topic, which explains why this occurs and how to fix it:
http://www.telerik.com/community/forums/aspnet-ajax/treeview/known-issues-and-breaking-changes.aspx 
 
All the best,
Bozhidar
the Telerik team

[John]

Thank you, I did see that note. Using an internal build is not an option for our environment and it also didn't explain why the trees behaved differently using the exact same dll. I did find the problem: the tree that works has a NavigateURL specified for the nodes, and the other tree does not. I can add it to the "broken" tree, but it degrades the performance, adding a click event when we don't need it. I'm guessing I need to trap & cancel the click event client-side?

[Bozhidar]

Hi John,

The fix will also be available in our upcoming Service Pack, which should come out in two weeks.

About the different behavior, when you set a NavigateUrl to a treenode, the text of the node is rendered inside a <a href> tag, as opposed to a <span> tag, which is the normal case. With the current implementation of the encoding mechanism in version 2012.1.215 this causes the text not to be encoded.

This is one of the problems that led to the decision to fix the whole encoding mechanism and introduce a property that controls whether the text should be encoded. I strongly recommend upgrading to the Service Pack once it comes out, since all these issues are already fixed.

However if you want to use the 2012.1.215 version and cancel the default behavior of the link generated by setting the NavigateUrl property, you can do it by simply removing the href attribute of the link on the OnClientLoaded event:

function clientLoad(sender) {
    var nodes = sender.get_allNodes();

    for (var i = 0; i < nodes.length; i++) {
        $telerik.$(".rtIn", nodes[i].get_element()).removeAttr('href');
    }
}

 
Greetings,
Bozhidar
the Telerik team

[Becky]

Thank you, Bozhidar! Knowing that the service pack is only 2 weeks away is good news. Thank you also for the workaround - this is very helpful in case I am pushed to go live sooner.

-Becky