Slow closing RadWindow in Internet Explorer

8 posts, 0 answers
  1. Bogdan
    Bogdan avatar
    2 posts
    Member since:
    Jul 2014

    Posted 24 Jul 2014 Link to this post

    I have a RadWindow inside a RadWindowManager (with NavigateUrl) that closes really slow but only in Internet Explorer (including 11). It only occurs when the window is maximized. The problem becomes very noticeable when there are many grid items in the window. Closing takes up to 15-20 seconds. Profiling shows that the offsetWidth function in IE takes a really long time. Chrome and Firefox are instant.

    I tried many configuration options and it seems that the only way to solve this issue is by not having the window maximized. Also, if I just delete the window manually, everything works quickly. Setting DestroyOnClose = true does not solve this problem either. What are the extra calculations that are happening on close event? Is there a way to avoid them?
  2. Bogdan
    Bogdan avatar
    2 posts
    Member since:
    Jul 2014

    Posted 24 Jul 2014 Link to this post

    Attached a screenshot of the profiler. (Got a 500 error when posting it with the original post).

    Thanks
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Marin Bratanov
    Admin
    Marin Bratanov avatar
    3599 posts

    Posted 28 Jul 2014 Link to this post

    Hello Bogdan,

    Can you confirm whether you have AutoSize enabled? This is one of the few features that will do calculations based on the offsetWidth of an element, especially after setting an element width to 1px. It should not, however, be executed when the RadWindow is closed.

    It is possible that autosizing or other custom logic that causes the delay is triggered by an event handler, e.g., to the OnClientBeforeClose or to the OnClientClose event. Thus, I would advise checking for such code to see if this is the root cause.

    Another suggestion I can offer is using the OnClientBeforeClose event to hide the RadWindow popup element with a script, e.g.:

    function OnClientBeforeCloseHandler(sender, args) {
        if (sender.isMaximized() && $telerik.isIE)
            sender.get_popupElement().style.display = "none";
    }

    to see if this makes a difference, at least to the user experience.

    With this information, it will be very difficult to offer a concrete answer. If you can send us a small runnable sample that shows the issue you observe we could profile it too and see what is going on.

    Regards,

    Marin Bratanov
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
  5. Solution Centre
    Solution Centre avatar
    2 posts
    Member since:
    Sep 2015

    Posted 01 Feb Link to this post

    We are also facing a very similar issue in IE (especially in IE8). When we close a window it can take 5+ seconds for it to disappear but it is instant on Chrome. I have gone through our code and disabled everything that happene OnClientClose or OnClientBeforeClose but this has made no difference.  The JS function we use to close the window is also extremely simple

    function closePopup() {
    var oWindow =GetRadWindow();
     if (oWindow != null) {
       oWindow.close();
    }
     return false;
    }

    I have run the profiler in IE8 developer tools and have attached the results. Any help you could give would be greatly appreciated

     

    Cheers,

    Joe

  6. Solution Centre
    Solution Centre avatar
    2 posts
    Member since:
    Sep 2015
  7. Stamo Gochev
    Admin
    Stamo Gochev avatar
    157 posts

    Posted 02 Feb Link to this post

    Hi Joe,

    I have already handled your support ticket, so I am pasting my answer here as well. It will be best if we can continue the discussion in the ticket in order not to duplicate it in this forum thread.

    Can you send me a sample page that reproduces the issue, so I can investigate it on my side? It will be helpful if you can isolate the scenario, so that there are no dependencies on additional JavaScript code. This will allow me to make a deeper analysis of the problem and provide you with further suggestions.

    In addition, can you give me more information on the following questions:
    Regards,
    Stamo Gochev
    Telerik
    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 Feedback Portal and vote to affect the priority of the items
  8. michael
    michael avatar
    2 posts
    Member since:
    Apr 2016

    Posted 04 Sep Link to this post

    Was this issue ever resolved. I have exactly the same problem. The rad window closes instantly in Chrome and Edge - and some small radwindows on IE 11, but for a RadWindow with more controls in it, it can take 10 or 15 seconds to close in IE 11. Unless I can fix this, I will have to go back to using popup windows rather than radwindows - something I do not want to do.
  9. Stamo Gochev
    Admin
    Stamo Gochev avatar
    157 posts

    Posted 07 Sep Link to this post

    Hello Michael,

    The problem has been resolved according to the described scenario in a separate support ticket that is not visible in the forum.

    If you are facing any issues with RadWindow, please open a new forum thread with a detailed description of the problem. This will ensure that we will keep the forum threads concise and dedicated to a specific case.

    I want to kindly ask you to attach a sample page that reproduces the issue in the new ticket, so we can investigate it.

    Regards,
    Stamo Gochev
    Telerik by Progress
    Do you need help with upgrading your ASP.NET AJAX, WPF or WinForms projects? Check the Telerik API Analyzer and share your thoughts.
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017