ProWorks Blog

IE 11 doPostPack and JavaScript Errors

By Rob Birdwell     Wednesday, January 08, 2014     javascript, internet explorer, bugs
 15 16 ShareThis

Recently we've been hearing from our clients and partners about trouble with Internet Explorer 11 and certain links not working on their web sites.  Here are the typical conditions:

  • the site uses .NET 
  • the server and/or .NET instance on the server is a few years old
  • the host server may not have the latest .NET patches (i.e., .NET 4.5)
  • the links that are not working involve some form of postback; this can include buttons, image buttons and/or hyperlinks - any element that invokes postback.

If upgrading the server with a "hot fix" patch is not an option, there's another low-impact soltution that seems to do the trick:

In your master page (below the @ Master directive) add the following lines:

<script runat="server">

protected override void OnInit(EventArgs e)
Page.ClientTarget = "uplevel";


I wouldn't regard this as anything but an interim soltuion.  But for older sites this may be one of the only options.

Other resources:

 15 16 ShareThis
comments powered by Disqus
comments powered by Disqus

3 memorable comments for "IE 11 doPostPack and JavaScript Errors"

  1. Posted 1/9/2014 10:16:15 AM

    Another Umbraco fix for RTE here:

  2. Posted 2/24/2014 3:03:41 PM

    Check this out. This explains a lot: One of the comments half way down the page explains that we can add the <clientTarget> element to the web.config under system.web. This helps IIS do its magic. <clientTarget> <add alias="ie11" userAgent="Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko" /> </clientTarget> This worked on the site that I was just seeing problems on. This is the MSDN documentation of the clientTarget element: It says that this is the default configuration: <clientTarget> <add alias="uplevel" userAgent="Mozilla/5.0 (compatible; MSIE 6.0; Windows NT 5.1)" /> <add alias="downlevel" userAgent="Generic Downlevel" /> </clientTarget> That's why your code up above did what it was doing.

  3. Posted 2/27/2014 6:52:14 PM

    My above fix stopped working for some reason. I had to go searching for a new one. Found it. Follow this guys instructions (, but if you try the .browser approach, remember to touch an existing .browser file after uploading your own .browser file. New .browser files aren't recognized immediately. They need to be rebuilt or something. Touching an existing .browser file will cause new .browser files to be recognized.