RadSplitter Height Percentage in ascx

[Tarun]

Hi, I am trying to make my splitter fit into the div that i specify.
Following code works perfect when placed inside aspx, but the UI changes (radSplitter now takes default width and height of 400px) when the same code is places inside the ascx.

I am not sure, why ? Ideally, the RadSplitter should use the absolute dimensions of the container to set its width and height.
Why should i bother to set the dimensions for all parent containers ?? The moment i specify absolute values for the container, the child controls should use those values.

Please correct me if my understanding is wrong.

<div style="width: 700px; height: 500px; border: 2px solid orange;">

<asp:ScriptManager ID="ScriptManager1" runat="server" />

    <telerik:RadSplitter ID="SplitterHorizontal" runat="server" height="100%" width="100%" Scrolling="None">

        <telerik:RadPane ID="LeftPane" runat="server" width="30%">           

            <telerik:RadSplitter ID="VerticalSplitter" Orientation="Horizontal" runat="server">

                <telerik:RadPane ID="LeftTopPane" runat="server" style="height:50%">

                </telerik:RadPane>

                <telerik:RadSplitBar ID="HorizontalSplitBar" runat="server" CollapseMode="Forward" />

                <telerik:RadPane ID="LeftBottomPane" runat="server" height="50%" >                   

                </telerik:RadPane>

            </telerik:RadSplitter>       

        </telerik:RadPane>

        <telerik:RadSplitBar ID="VerticalSplitBar" runat="server" CollapseMode="Forward" />

        <telerik:RadPane ID="RightPane" runat="server" width="70%">

        </telerik:RadPane>

    </telerik:RadSplitter>

</div>

[Dobromir]

Hi Tarun,

Yes, you are correct, if the direct parent of the splitter have fixed width / height you do not need to set height to the rest of the parent elements.

I tried to reproduce the problem with the provided code snippet but to no avail. For your convenience I have attached my test page, could you please modify it to the point where the problem occurs and send it back so we can examine and debug the issue locally?

Regards,
Dobromir
the Telerik team