Window Resize Lag (~.5 sec)

2 posts, 0 answers
  1. Michael Ash
    Michael Ash avatar
    6 posts
    Member since:
    Apr 2010

    Posted 20 May 2010 Link to this post

    I'm using nested splitters (splitters occupy entire page) with almost nothing but text inside, and when the browser window is re-sized there is a noticeable lag for the panes to refit in the window.  Use of "VisibleDuringInit" only works when the page is loaded.
    This is not an issue with your examples, since the splitters don't get resized with the browser window.
    I saw a post here from 2007 that recommended enclosing the Radpane contents in <div RadResizeStopLookup="true" RadShowStopLookup="true" >...</div> with some additional JavaScript.
    I attempted this, and there was no difference.
    Is there any way to get rid of this lag or disguise it.
    This doesn't happen when I use frames (which I would really prefer not using). It doesn't happen with Obout's splitters, but their support is not good, and I really like everything else about your products.
    If I can't resolve this problem, I'll probably have to use your system with frames (if that doesn't create even more obstacles).

    Best regards,
  2. Tsvetie
    Tsvetie avatar
    1517 posts

    Posted 25 May 2010 Link to this post

    Hi Michael Ash,
    The workaround that you found was for RadSplitter for ASP.NET and in case I understand you correctly, you are using RadSplitter for ASP.NET AJAX. That is why, applying it will not make a difference.

    First of all, let me explain how a splitter control that is defined in percentages behaves. Once the splitter is initialized, it calculates the size of its parent element and based on that size, the splitter calculates its own size in pixels. After that, the splitter calculates and sets the size of all its elements and panes in pixels. Basically, this operation - setting the size (width and height) of an element with JavaScript, is not a slow operation. However, in case you add a lot of HTML in that element, the time the browser takes to repaint that element increases. The more HTML you add, the more time the browser needs to repaint the element. We have reduced the times the splitter sets size to its elements to a minimum. Even so, however, in case you add a lot of HTML to the splitter panes, the splitter control will be slow.

    Having said that, I have the following suggestions for you:
    1. Reduce the HTML that you show in the splitter panes. For example, in case you are using a grid, you can take advantages of its paging or virtual scrolling functionality. For other controls (e.g. treeview), you can use the load on demand functionality.
    2. Reduce the number of nested splitters you have.
    3. Reduce the number of splitters with size in percentages.
    4. When you test your application, set "debug=false" in your web.config file.
    5. Take advantage of our RadScriptManager and RadStyleSheetManager controls.
    6. Refer to the following article for general tips - Optimizing output, page load time and the overall performance of RadControls for ASP.NET AJAX.

    Kind regards,
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
  3. DevCraft R3 2016 release webinar banner
Back to Top