Hi Adelhard,

I tried to replicate your issue in my local end. Unfortunately, this issue doesn't occurs in my local end. This issue might be happen because there are some javascript errors from Combo_Kunde WebCombo. Is there any working sample or javascript error that you can show us so I can replicate this issue in my local end? Perhaps, you can copy the javascript error in your console window inside your web browser to give me clue what issue that occurs in your page. Look forward to hear any feedback from you so I can help you further.

Regards,
Bernard

Hi Raj,

I can replicate your issue in our local end. After checking this issue, we have consider this issue as bug and I have made a work item regarding this issue. We are really sorry for this inconvenience and I will let you know any news regarding this work item from our developer team. Thank you for your valuable feedback.

Regards,
Bernard

Hi Daniel,

I can replicate your issue in here. I will report this to our developer team and I will let you know any feedback from our developer team regarding this issue.

Regards,
Bernard

Hi Adelhard,

Have you put height for each element above WebCombo tag? WebCombo will preserve its Resultbox to appear below WebCombo if your page still have area below WebCombo (WebCombo doesn't appear on below of your page). You can download my sample here. In my sample I put this style so html, body and form tag have 100% height which is default behavior in IE9 and earlier. 

<style type="text/css">
    html, body, form
    {
        height: 100%;
        margin: 0px;
        padding: 0px;
        width: 100%;    
    }
</style>

Please also use RenderingMode HTML5 and doctype HTML5 when using WebCombo in IE11 and IE10. This is necessary because IE10 and IE11 used HTML5 doctype as standard doctype for its rendering. Hope this helps.

Regards,
Bernard

Hi Ravinder,

In my sample, I'm using HiddenField to send WebTreeView value to server side. Then by using WebCombo value as nodes that should be attached and HiddenField value as target node, in server side I attach all child nodes to target node. Although in server side, I persist that value in static variable so whether I add another nodes to WebTreeView, the previous WebTreeView state still can be read in WebTreeView's InitializeChildNodes event.

Maybe your issue happen because your page doesn't persist the previous state of WebTreeView when your page do postback method. When postback all state and changes inside WebTreeView will be cleared because it will call initialize method. So I think it will need some variable to persist the previous state of WebTreeView so I won't replace your nodes when you do postback. Hope this helps.

Regards,
Bernard