Hi Ravinder,

In my sample, I have add a button that could postback the page. When postback, in my sample, I add the value in server side so WebTreeView will have another child regarding the value of WebCombo that will be bound in server side. In detail way, you could see the scenario of my sample in this link. The issue that you told us, also doesn't happen in my local end. Perhaps if this sample doesn't meet your requirement, could you modify my sample or give us a simple sample so I can trace where the problem comes from? Look forward to hear any feedback from you so I can help you further.

Regards,
Bernard

Hi Steve,

I think there were some issue or bug in our WebTextEditor control. Perhaps to resolve your issue, you could use Chrome for now until we update our community forum. Soon, we will update our community forum with new feature and we will make sure our WebTextEditor control is not bugged in community forum. Thank you for your valuable feedback.

Regards,
Bernard

Hi Ravinder,

Regarding to your scenario above, i have made you a sample. In my sample, I tried to add the node in server side and client side in IE8 when using XHTML doctype. Unfortunately, this issue doesn't occurs in our local end. Could you give us a simple sample or modify our sample so I can replicate the issue here? Please also ensure if you're using the latest version of WebTreeView and our framework assemblies so there won't be any major bug in your local end. You can download my sample here and I will looking forward to your feedback so I can help you further.

Regards,
Bernard

Hi RIchard,

You can search our post and thread by using this page:

http://intersoftpt.com/Community/Search.aspx?as=1

You could also filter our ClientUI community page using filter option that we provided inside this page:

http://intersoftpt.com/Community/ClientUI

If you couldn't see the filter box, please click Show Options button in that page to show the filter option for that community forum.

Hope this helps.

Regards,
Bernard

Hi Ravinder,

This issue might be happen because you're using HTML5 doctype which not supported by IE8. I tried to replicate your issue here by using XHTML doctype and XHTML RenderingMode. Unfortunately, this issue doesn't happen in our local sample. And as you said before, this issue happen when I used HTML5 doctype in IE8.

By using HTML5 RenderingMode, WebTreeView will rendered properly in all modern browser which support HTML5 doctype. Perhaps to resolve this issue, you can use XHTML doctype. You must also consider that IE11 and IE10 browser only support HTML5 as its standard doctype. Hope this helps.

Regards,
Bernard