CODEWITHSUNDEEP
asp.net.netasp.net-ajaxinternet-explorer-11
tpe
tpe

Reputation: 115

Internet Explorer 11 gives script error in PageRequestManager.js

I'm using ASP.NET 4.5 on the server and I have a .NET Windows application with a Web Browser control that navigates to the web page on the server.

If I run the Windows application on a system with Internet Explorer 11, I get a script error: "Object doesn't support property or method 'attachEvent'" when navigating to another page. The script file is ScriptResource.axd so it isn't any of my scripts.

I do know that Internet Explorer 11 doesn't support attachEvent anymore (replaced with attachEventListener?). That is however not of much help here, as the javascript is part of the framework, not in my code.

I found the javascript source for the framework here: http://ajaxcontroltoolkit.codeplex.com/SourceControl/latest#Client/MicrosoftAjax/Extensions/Sys/WebForms/PageRequestManager.js

// DevDiv Bugs 100201: IE does not set referrer header on redirect if you set window.location, inject anchor node instead
// dynamic anchor technique only works on IE
if (Sys.Browser.agent === Sys.Browser.InternetExplorer) {
    var anchor = document.createElement("a");
    anchor.style.display = 'none';
    // cancel bubble so body.onclick is not raised
     anchor.attachEvent("onclick", cancelBubble);
    // more code...
}

This is the Sys.Webforms.PageRequestManager module that is part of the core ASP.NET framework as far as I understand.

The line that performs attachEvent gives script error on Internet Explorer 11, but works great on older versions of Internet Explorer.

How to fix this problem? Are there any known workarounds? I couldn't fine any updates for this.

Upvotes: 5

Views: 10284

Answers (2)

Sabrina
Sabrina

Reputation: 298

I got that problem with jQuery 1.10 and it seems, that IE11 lacks the support of "attachEvent" which is used in jQuery and which seemed to be used by your framework as well. There is a Microsoft bugticket for that: Bugticket attachEvent IE11

I've found a solution in the related jQuery bugticket. Just insert the following code before your framework:

var isIE11 = !!(navigator.userAgent.match(/Trident/) && !navigator.userAgent.match(/MSIE/)); 
if (isIE11) {
    if (typeof window.attachEvent == "undefined" || !window.attachEvent) {
        window.attachEvent = window.addEventListener;
    }
}

You first check if the browser is IE11 and then bind the attachEvent listener again so the error doesn't occur again.

Upvotes: 3

bastos.sergio
bastos.sergio

Reputation: 6764

Try forcing the browser to render in IE 10 mode...

<meta http-equiv="X-UA-Compatible" content="IE=10" />

Upvotes: 6

Related Questions