RadSplitter height 100%

32 posts, 0 answers
  1. Vessy
    Vessy avatar
    1664 posts

    Posted 28 Jun 2013 Link to this post

    Hello Steve,

    The Splitter (and all RadControls as a whole) is made of HTML and as such they obey some rules which are true in general for the technology itself. As every HTML element, in order to calculate correct size in percentages, the Splitter should have only parents with set size (up to a parent with a fixed height). This is why the control has some initially set fixed height (the mentioned 400px), in order to render itself in case its parent height is not properly configured.

    Since we cannot change this behavior for the splitter, the only thing left we could do in this case is to iterate through all the parents and set their height explicitly. However this is not a good solution due to many facts, e.g the following ones:

    1) It is not a good practice to silently change the rest of the page
    2) Any sizes which were set explicitly by the developer will break
    3) There are scenarios in which setting 100% height for the parent is wrong, depending on the scenario. You can have splitter set to 100% but its parent can dynamically change size.
    4) Iterating through all the parents in the hierarchy will cause performance slow, while simply setting a CSS to the right elements is much better.

    Having in mind the above, we think that it is much better to provide resources on how to configure the layout of the Splitter. You can find this described in details in our online demo below:
    Resize with Window

    I hope that my reply is detailed enough, in case you have additional comments or some suggestions for a better solution, we will be glad to hear it.

    Kind regards,
    Veselina Raykova
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed now.
  2. Steve
    Steve avatar
    7 posts
    Member since:
    Jun 2012

    Posted 17 Jul 2013 Link to this post

    Veselina  - thank you for your response.

    On another inspection of the details on the link you provided, a small detail at the bottom about VisibleOnInit = False has helped me avoid the issue of the appearance of the Splitter (prior to resizing) looking very unsightly on the page for a second or so (on large HTML documents).
Back to Top