This is a migrated thread and some comments may be shown as answers.

[Solved] RadWindow. When DestroyOnClose="false" a parent's disabled control will fire an error with mouse-over

6 Answers 390 Views

Window

This is a migrated thread and some comments may be shown as answers.

Mark asked on 02 Nov 2007, 12:56 AM

Hi

I'm using Visual Studio 2005, C#, ASP.NET AJAX.

I have a page that has controls which can be disabled, e.g., Textbox, etc.

It can also call a RadWindow. After the RadWindow closes, back on the parent page if I move my mouse over a disabled control it will fire an error if the RadWindow DestroyOnClose = "False" (IE7 seems to fire endless mouse-over events).

That error is: Microsoft JScript runtime error: Sys.ArgumentException: Value must be a DOM element. Parameter name: element.

I found a link which suggests that it could be a known Microsoft error: http://forums.asp.net/p/1151199/1918939.aspx#1918939

Please note that this error does not occur if I set the RadWindow DestroyOnClose = "true" (or don't use the RadWindow at all).

However I need to use this RadWindow several times and as such I don't want it destroyed.

I hope this makes sense and I'm happy to provide a code example if needed.

Kind regards

Mark Eaton

6 Answers, 1 is accepted

answered on 07 Nov 2007, 04:20 PM

Hello Mark,

The problem is in the ASP.NET AJAX framework itself, so at this point we cannot say for sure if we will be able to fix it. From the forum thread that you provided we see that MS is aware of this issue and it is logged in their bug tracking system - hopefully they will fix it in the future. If for some reason this doesn't happen soon, we will do our best to find an appropriate solution from our side, but it is not an easy task.

For the time being the only suggestion that we have is not to disable the controls but to set their visibility to hidden. This way they will not be visible to the client but they will still be present and your layout will be the kept the same.

All the best,
Georgi Tunev
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

answered on 08 Nov 2007, 04:18 PM

Hello Mark,

The reason for the problem in the scenario with RadWindow is that by design when a RadWindow is closed, its object is not destroyed - basically, the RadWindow remains but is hidden on the page. In this case however some handlers (specifically the ones responsible for the RadWindow resizing) stay attached which leads to invoking the bug in ASP.NET AJAX.
When DestroyOnClose is set to true, the RadWindow object is destroyed and the problem does not exists.

We will try to find an appropriate solution on our side - like detaching the handlers when a RadWindow is hidden, however we need to investigate all pros and cons for such approach and this will take some time. For the time being you can either hide your disabled elements as suggested in my previous reply, or alternatively you can disable the resizing feature of RadWIndow.
e.g.:

<form id="form1" runat="server">  

    <asp:ScriptManager ID="ScriptManager1" runat="server" /> 

    <div> 

        <input type="text" size="15" id="TextBox1_text" disabled="disabled" /> 

        <input id="OpenWindowButton" type="button" value="Open Window..." onclick="openWindow();" /> 

        <telerik:RadWindowManager Behavior="Close, Maximize, Minimize, Move, Pin, Reload" ID="WindowManager" runat="server">  

        </telerik:RadWindowManager> 

    </div> 

    <script type="text/javascript">  

        document.getElementById("TextBox1_text").value = "The Empty Message";  

        function openWindow()  

        {  

            var oWnd = window.radopen("TestWindow.aspx","TestWindow");  

        }  

    </script> 

</form>

Greetings,
Georgi Tunev
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center