RadAjaxLoadingPanel freezing

4 posts, 1 answers
  1. Daron
    Daron avatar
    80 posts
    Member since:
    Dec 2007

    Posted 12 Feb 2008 Link to this post

    Hi all,

    I'm pretty new to the whole ajax thing so don't be too harsh on me. Does anyone knows if it's possible to prevent the ajax loading gif from freezing up (ie, stop moving) just before outputting to the screen?

    I have a massive datagrid that's loaded "ajaxically" and just as the browser is about to draw out the rows (which takes several seconds) the gif freezes and it looks to the user as though the site has frozen. I want it to keep spinning the entire time. I guess we're getting into dangerous thread-territory here right?

  2. Answer
    Neil avatar
    16 posts
    Member since:
    Mar 2007

    Posted 13 Feb 2008 Link to this post

    I may be way off here, but I think the loading panel stops moving because your browser has begun processing the data from the server. We have a TreeView with about 1500 nodes that are added dynamically, and we can always tell exactly when the server's done processing and the data's at the client's browser - the indicator stops spinning. I suspect it's because browsers limit the Javascript threads each window or tab gets, but I don't know that for a fact. So if all of my guesses are correct, there's really nothing you can do since it's an intentional browser limitation.
  3. Jason Maronge
    Jason Maronge avatar
    321 posts
    Member since:
    Jan 2005

    Posted 13 Feb 2008 Link to this post


       Which browser are you seeing this in.  I used to have the same issue with IE6.  When we used IE7 the freezing was reduced big time.  Cannot remember what Firefox did.  I don't really think there is much that can be done about it though. 

  4. Daron
    Daron avatar
    80 posts
    Member since:
    Dec 2007

    Posted 14 Feb 2008 Link to this post

    Hi Ralph & Jason,

    Thanks for your responses. Yes I'm using IE6, But FF appears to do the same thing.

    I had my suspicions that it was a browser-threading issue but was hoping otherwise. Oh well ... back to the drawing board!

Back to Top