We have started experiencing a very frequent problem with our dialog windows resulting in a "null is not null" Javascript error. It has started happening since the Q1 update. We have a modal window template defined on the MasterPage like this:
This is the only RadWindowManager defined in our application. Various dialogs use this same template and are launched with code like this:
The problem is that getWindowByName frequently returns NULL, but not always. We can restart IIS and it will work again for a little while, but then on another dialog window using the same ModalWindow template the call will fail and result in a "null is not null" Javascript error.
What would be causing the ModalWindow template to not be initialized or present?
As a "best practices" question, should I even be doing it this way to begin with? Does the modal window template introduce overhead on every page in the application that is not always needed? I like having the settings defined once that are used everywhere, but if it's better to do a "open" and create a new window every time we need it then I can do it that way.
Thanks,
Terry
<telerik:RadWindowManager ID="ieRadWindowManager" runat="server"> |
<Windows> |
<telerik:RadWindow ID="ModalWindow" Modal="true" Behaviors="Close,Resize,Move" VisibleOnPageLoad="false" VisibleStatusbar="false" ReloadOnShow="true" ShowContentDuringLoad="false" runat="server" /> |
</Windows> |
</telerik:RadWindowManager> |
This is the only RadWindowManager defined in our application. Various dialogs use this same template and are launched with code like this:
function showChartOptions(url) |
{ |
var manager = GetRadWindowManager(); |
var modalWindow = manager.getWindowByName("ModalWindow"); |
modalWindow.add_close(OnChartOptionsClose); |
modalWindow.setSize(600,450); |
modalWindow.setUrl(url); |
modalWindow.show(); |
} |
The problem is that getWindowByName frequently returns NULL, but not always. We can restart IIS and it will work again for a little while, but then on another dialog window using the same ModalWindow template the call will fail and result in a "null is not null" Javascript error.
What would be causing the ModalWindow template to not be initialized or present?
As a "best practices" question, should I even be doing it this way to begin with? Does the modal window template introduce overhead on every page in the application that is not always needed? I like having the settings defined once that are used everywhere, but if it's better to do a "open" and create a new window every time we need it then I can do it that way.
Thanks,
Terry