FIX Under IE10 a Modal RadWindow shown in the Sys.Application.Load event inside a RadAjaxPanel inside another RadWindow throws a JavaScript error

Progress® Telerik® UI for ASP.NET AJAX Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 27 Jun 2016 08:45 by Tonino

ADMIN

Marin Bratanov

Created on: 07 Dec 2012 08:56

Category: Window

Type: Bug Report

FIX Under IE10 a Modal RadWindow shown in the Sys.Application.Load event inside a RadAjaxPanel inside another RadWindow throws a JavaScript error

This is related to a browser bug in accessing the document.activeElement property inside an iframe under IE9 and IE10.

See this KB article for additional information and examples: http://www.telerik.com/support/kb/aspnet-ajax/window/modal-radwindow-in-radwindow-in-ie9-and-ie10.aspx .

There are several possible workarounds:
1) remove the Modal feature.
2) Replace the opening logic with the one from this thread ( http://www.telerik.com/community/forums/aspnet-ajax/window/opening-radwindow-from-the-server.aspx ) and add a small timeout before showing the RadWindow. Even 0ms could suffice so the browser has an active element
3) Replace the RadAjaxPanel with an ASP UpdatePanel with UpdateMode set to Conditional
4) Add a function that will provide a focused element and call it in the OnClientBeforeShow event of the RadWindow
5) Add that function and call it in the ResponseScripts of the RadAjaxPanel
 The function could look like this: function fixIE() { document.documentElement.focus();} where, of course, you can focus some other element on the page.

A sample is attached.

Attached Files:

PossibleFixes.zip

4 comments

Tonino

Posted on: 27 Jun 2016 08:45

deleted by Tonino

Posted on: 13 Jul 2013 01:19

Telerik developers should know know better than to get stuck with each version of IE's nuances.  One way to fix issues with Telerik javascript error is to either override their event attachments or setTimeout to make sure other events are fired in the proper order.  Shame on you Telerik.  If you Telerik call yourself web developers, don't make you code trapped to a specific version of a browser.

Jeneby Mathews

Posted on: 23 Jun 2013 01:25

Totally agree Shawn.

It's ridiculous that bugs like this have become acceptable and we are expected to implement and maintain the workarounds. I wonder what my client's would do if I gave them software that required workaround like this.

Known bugs should be fixed by Telerik.  Simple as that...... (Use the time spent on developing workarounds to develop fixes.

Shawn Krivjansky

Posted on: 22 Mar 2013 17:08

Don't know how anybody could "dislike" a fix for this.  Moreover, I don't see why Telerik scripts can't be adjusted (somehow) to account for this.  IE has had 1000s of bugs/quirks over the years... and I don't have 1000s of "fixIE" scripts in place, so Telerik must be doing something to hide that mess from me.  This is one other mess I would like hidden from, so I don't need to create/maintain code like this.  I buy and use the Telerik control suite to get away from this kind of stuff.