‘WebForm_DoPostBackWithOptions’ is undefined in IE11 Preview

IE11 is coming. I just installed the developer preview version. However, if I run some of my web application and I got the error WebForm_DoPostBackWithOptions is undefined.

The error popped up when I was playing with the autopostback DropDownList.

Moreover, it looks like there was a similar issue with IE10 before:



Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

I had a similar issue with Internet Explorer 11 not being detected correctly by .NET 4.0 framework. Here’s how I worked around the problem:

Installing the suggested patches didn’t do the trick. After digging deeper into the issue, I found that although the http://support.microsoft.com/kb/2836939 patch is installed on the server, the browser is still recognized as Mozilla with version 0.0 on the server. After additional research I found that if you have any .browser file in your site’s app_browsers folder, the version detected on the server is wrong, namely Mozilla 0.0.

To work around the issue I created a custom .browser file in the app_browsers directory with the following content:

  <browser id="IE11" parentID="Mozilla">
      <userAgent match="Trident/7.0; rv:(?'version'(?'major'd+)(.(?'minor'd+)?)(?'letters'w*))(?'extra'[^)]*)" />
      <userAgent nonMatch="IEMobile" />
      <userAgent match="Trident/(?'layoutVersion'd+)" />
      <capability name="browser"              value="IE" />
      <capability name="layoutEngine"         value="Trident" />
      <capability name="layoutEngineVersion"  value="${layoutVersion}" />
      <capability name="extra"                value="${extra}" />
      <capability name="isColor"              value="true" />
      <capability name="letters"              value="${letters}" />
      <capability name="majorversion"         value="${major}" />
      <capability name="minorversion"         value="${minor}" />
      <capability name="screenBitDepth"       value="8" />
      <capability name="type"                 value="IE${major}" />
      <capability name="version"              value="${version}" />

  <!-- Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11,0) like Gecko -->
  <browser id="IE110" parentID="IE11">
      <capability name="majorversion" match="11" />

      <capability name="ecmascriptversion"    value="3.0" />
      <capability name="jscriptversion"       value="5.6" />
      <capability name="javascript"           value="true" />
      <capability name="javascriptversion"    value="1.5" />
      <capability name="msdomversion"         value="${majorversion}.${minorversion}" />
      <capability name="w3cdomversion"        value="1.0" />
      <capability name="ExchangeOmaSupported" value="true" />
      <capability name="activexcontrols"      value="true" />
      <capability name="backgroundsounds"     value="true" />
      <capability name="cookies"              value="true" />
      <capability name="frames"               value="true" />
      <capability name="javaapplets"          value="true" />
      <capability name="supportsCallback"     value="true" />
      <capability name="supportsFileUpload"   value="true" />
      <capability name="supportsMultilineTextBoxDisplay" value="true" />
      <capability name="supportsMaintainScrollPositionOnPostback" value="true" />
      <capability name="supportsVCard"        value="true" />
      <capability name="supportsXmlHttp"      value="true" />
      <capability name="tables"               value="true" />
      <capability name="supportsAccessKeyAttribute"    value="true" />
      <capability name="tagwriter"            value="System.Web.UI.HtmlTextWriter" />
      <capability name="vbscript"             value="true" />

A similar approach is suggested in the following article:
doPostback failing in IE 11+ Windows 8.1

I would like to clarify that the issue is happening only with .NET 4.0. With .NET 4.5, the browser and its version are detected correctly.

Method 2

Finally, I found the solution, Thanks Scott Hunter’s advice.

If you want to solve the IE11 issue, please install the hotfix below.

Method 3

I tried every patch that I’ve seen listed on the internet, including the ones listed here. The only thing that actually seemed to work was installing the .NET 4.5 Framework on the server.

Get it here: http://www.microsoft.com/en-us/download/details.aspx?id=30653

Hope this saves someone a few of the hours I’ve lost on this one.

Method 4

For anyone struggling to understand why user2919107’s answer above (putting a custom .browser file for IE11 in your App_Browsers folder) doesn’t work, try to touch an existing .browser file in your App_Browsers folder.

Simply creating/copying the IE11 .browser file doesn’t work. You need to touch an existing .browser file so that App_Browsers contents are re-compiled and taken into account.

Method 5

Yes, this is the same core issue, and it’s fixed by the June 2013 ASP.NET hotfix. See http://blogs.msdn.com/b/ieinternals/archive/2013/09/21/internet-explorer-11-user-agent-string-ua-string-sniffing-compatibility-with-gecko-webkit.aspx

Method 6

If you are running windows 2003 and are unable to apply any hotfix; try setting the ClientTarget property of the Page object in the Page_Init of your ASP.NET page to “uplevel”.

protected void Page_Init(object sender, EventArgs e)
    Page.ClientTarget = "uplevel";

Method 7

I was also having this problem. I tried everything short of installing .NET 4.5. I was just looking for a short term solution before we upgrade to .NET 4.5. Panagiotis Poulos was correct about the new .browser file. I touched an existing .browser file and my new IE .browser file is now being recognized. Everything works again as far as I can tell.

In short, follow this guys instructions, but if you try the .browser approach, remember to touch an existing .browser file after uploading your own .browser file.

Method 8

Found a temporary fix to this.

I tried applying the hotfix but I couldn’t get the hotfix to install. The error was: kb2600088 does not apply, or is blocked by another condition on your computer. Probably due to .NET 4.5, I googled abit but I didn’t want to uninstall .NET 4.5 so I didn’t follow through.

So, to get around the original problem, start IE11 and go to developer’s console by pressing F12. Under ‘Emulation’ tab, set document mode to ’10’ and under user agent string, set it to ’10’ as well. I believe it emulates IE 10 which works perfectly fine without having to run into this bug.

This is only a work around. Not a fix. Hope it helps those trying to get work done.

Method 9

If you downloaded IE 11 but use the original IE browser that came with Windows, the user agent of the browser is little bit different and the most upvoted answer will not work.

You just have to change this line:

<userAgent match="Trident/7.0; rv:(?'version'(?'major'd+)(.(?'minor'd+)?)(?'letters'w*))(?'extra'[^)]*)" />

to this:

<userAgent match="Trident/7.0;(?'someGarbage'[^'rv:']*) rv:(?'version'(?'major'd+)(.(?'minor'd+)?)(?'letters'w*))(?'extra'[^)]*)" />

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes
Article Rating
Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x