Hi Victor

  Many thanks for you reply. I am very new in windows dialog, so I did not know the conflict with the WARP control.

  In regarding the list bar, yes it is true I have not wraped it with the form. I was thinking to use this control as a link menu only.

  thanks again. I am going to make the changes now and see how it behaves :) .

I forgot to give you "move codes". Here dialog is moved out from undesired container and displayed on start:
<script type="text/javascript">
function initDialog(dialog, evtArgs)
{
 var elem = dialog.get_element();
 elem.parentNode.removeChild(elem);
 document.body.appendChild(elem);
 dialog.show();
}
</script>
<div style="position:absolute;left:200px;top:200px;width:300px;height:300px;overflow:auto;background:cyan;">
  <ig:WebDialogWindow ID="WebDialogWindow1" runat="server" Width="300px" Height="300px" Modal="true" WindowState="Hidden">
     <ClientEvents Initialize="initDialog"></ClientEvents>
  </ig:WebDialogWindow>
</div>

Hi Victor

  Thanks so much for replying me :) .

  Your answer is valid, but not for my pages. The form exist in the master page hence the childrem pages get the master form as their own form.

  if you have a look of the master page you would see something like that:

                    <!--Start of content-->
                    <form id="masterForm" runat="server">
                            <asp:scriptmanager ID="Scriptmanager1" runat="server"></asp:scriptmanager>
                            <asp:ContentPlaceHolder ID="cphGeneral" runat="server">
                            </asp:ContentPlaceHolder>       
                   
                    </form>
                    <!--End of content-->

  When the page is displayed in the browser, then a form is generated with the ID aspnetForm as follow:

                 <form name="aspnetForm" method="post" action="frmDetailsMaintenance.aspx" id="aspnetForm">

  So, I do not think that the form is the problem as this is alreading wrapping all the infragistic controls in the child pages.

  Do you have another suggestion? My users really like the idea of having floating windows with the content inside and I would be really embarresed if I tell them that is not posible now :( .

  Do you think is a bug of infragistic?

  I would reaaly appreciate any help... Thanks Victor

Hi,

I looked at attached codes and found unusual logic. I am in doubt that dot-net supports (or recommends to use) server controls located outside of form object. If it does, then Infragistics controls are not.

I suggest you to use form as a wrapper for all content, but not as a child located deep inside.