RadSplitter inside a Multipage RadPageView renders blank

2 posts, 0 answers
  1. Jay
    Jay avatar
    59 posts
    Member since:
    Apr 2009

    Posted 14 Dec 2011 Link to this post

    I've run into this a few times where I opt to use a RadSplitter to help organize my page instead of <div> tags and when I use it on more than one of the RadPageViews none of them appear?

    Here's a basic example of what I am seeing:

    Example #1: works fine (2 page views with only 1 having a splitter)
    <RadMultipage>
    <RadPageView1>
    <RadSplitter> RadPanes and markup </RadSplitter>
    </RadPageView1> 
    <RadPageView2>
    Regular HTML Markup
    </RadPageView2>  
    </RadMultipage> 

    Example #2: Both PageViews render as blank white space (2 page views with both having a splitters)
    <RadMultipage>
    <RadPageView1>
    <RadSplitter> RadPanes and markup </RadSplitter>
    </RadPageView1> 
    <RadPageView2>
    <RadSplitter> RadPanes and markup </RadSplitter> 
    </RadPageView2>  
    </RadMultipage>  

    Any ideas why this is happening? I hate to say i've gotten lazy but using Splitter controls without actually using splitter bars have become the most efficient way for me to get my markups to consistently fill the height and width 100%.

    Yes I have the base CSS setting HTML, Body, and form to 100% for both H and W.
    Thanks, Jay
  2. Dimitar Terziev
    Admin
    Dimitar Terziev avatar
    1266 posts

    Posted 19 Dec 2011 Link to this post

    Hello Jay,

    I've made a sample page based on scenario you have described trying to reproduce the experienced issue but to no avail. Could you please open a support ticket and provide a sample page demonstrating the problem so we could troubleshoot it locally.

    All the best,
    Dimitar Terziev
    the Telerik team
    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 their blog feed now
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top