hi,

thx for the suggestion, but i cannot remove the updatepanels. this code sample is only a little part of a big site where different parts of the page are updated independently.

i would be acceptable if i could update the tabcontent manually (even if postback is not originating from this control, like updatepanels conditional mode).

also, it does not work if i put a updatepanel around the webtab, but i need partial postbacks outside of the tab too.

to be clear, this worked with the old infragistic ultrawebtab. i'm in the process of converting the site to the new components and this is one of the last problems.

Hello,

Thank you for you update.

You can add update panel inside the ContentTabItem if you disable the Ajax .

You can set the new windowState inside the client side event function

<script type="text/javascript">

        function showWDW() {
            oWebDialogWindow1 = $find('<%= WebDialogWindow1.ClientID %>');
            oWebDialogWindow1.set_windowState($IG.DialogWindowState.Normal);
        }
    </script>
       
 <ig:WebTab ID="WebTab1" runat="server" Height="400px" Width="400px">
            <Tabs>
                <ig:ContentTabItem runat="server" Text="Tab 1" EnableAjax="False" AutoSize="False"
                    EnableRelativeLayout="false" EnableDynamicUpdatePanel="False" ScrollBars="Hidden">
                    <Template>
                        <asp:UpdatePanel ID="UpdatePanel1" runat="server">
                            <ContentTemplate>
                                <ig:WebDialogWindow ID="WebDialogWindow1" runat="server" UseBodyAsParent="false"
                                    WindowState="Hidden" Modal="true" InitialLocation="Manual" Moveable="true" Width="200px"
                                    Height="200px">
                                    <Header>
                                        <CloseBox Visible="true" />
                                    </Header>
                                    <ContentPane>
                                        <Template>
                                            <p>
                                                blah
                                            </p>
                                        </Template>
                                    </ContentPane>
                                </ig:WebDialogWindow>
                                <asp:Button ID="Button1" runat="server" Text="Button" OnClientClick="return showWDW();"
                                    OnClick="Button1_Click" />
                            </ContentTemplate>
                        </asp:UpdatePanel>
                    </Template>
                </ig:ContentTabItem>
                <ig:ContentTabItem runat="server" Text="Tab 2">
                </ig:ContentTabItem>
            </Tabs>
        </ig:WebTab>

Please let me know if this is acceptable for you.

Hi Sofia,

I am having issue with webtab and webDialogWindow.

Issue 1: WebDialogWindow displaying inside webtab.

issue 2: I am able to access parent page WebMenu and LeftMenu items when WebDialogWindow Opened

Issue 3 I tried to open DailogWindow of Window. again same issue.. displaying inside the 1st child.

<ig:WebDialogWindow ID="wbDialog" runat="server" Height="90%" Width="90%" UseBodyAsParent="true"
Modal="true" InitialLocation="Centered" Moveable="true" ModalTabIndices="false"
WindowState="Hidden">
<ClientEvents Initialize="wbDialogs_Initialize"></ClientEvents>
</ig:WebDialogWindow>

function wbDialogs_Initialize(sender, eventArgs) {
sender.get_element().style.position = 'static';
}

I tried in many ways, but I couldn't resolve the issue. Can you please help me in this.

Thank you.

i found a way to put the dialog outside of the webtab. it works for me now, but i think this behavior is broken nonetheless.

hi, there are 2 problems with this:

1) i need to set the dialog with values from the database, so i need the show it from code behind.

2) now the dialog is maximized inside of the webtab, i need it maximized on the browser screen. i tried playing around with usebodyasparent, but this does not make a difference.