Incompatibility between Internet Explorer 10 and UpdatePanel over .NET Framework 4.5 - by Parsa.Laylazi

Status : 

 


7
0
Sign in
to vote
ID 805516 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 10/15/2013 4:50:01 PM
Access Restriction Public

Description

I am not good in English texting, I apologize in advance.

It seems there are one(or some) incompatibility between Internet Explorer 10 and Microsoft AJAX Server Controls over .NET Framework 4.5.
When developers use controls that fire server event (like Button) inside an UpdatePanel, after an asynchronous PostBack, a JavaScript error has been thrown:

------------------------
Unhandled exception at line 885, column 13 in http://localhost:2950/ScriptResource.axd?d=JnUc-DEDOM5KzzVKtsL1tfpm2gWZV_t6iXj83pYkHGARzJmy7CXdl0pZmdE9sRnViPMh4zK5Al3zPP5VNzptaA9WUrXtQEzBihVVecQ4twMCZQGqumTigd7pRlNgb1uzd2BDIKqc4kXlOo8ryrTbrLjdeb5tELjS8oXkvgqZ_v2T2NTPcbG4HOmeks_0sHJg0&t=6119e399

0x800a139e - JavaScript runtime error:

Sys.WebForms.PageRequestManagerParserErrorException:

The message received from the server could not be parsed.
------------------------

This means async PostBacks has been processed as normal PostBack and their response is not MS AJAX friendly.

After more than 6 months of researches, I found that UpdatePanel does not register control as PostBackControl on ScriptManager when Internet Explorer 10 used as client.
Also I found there are two solutions to fix this situation.

1. Using X-UA-Compatible meta tag that set Internet Explorer Document Mode as IE9.
2. Using RegisterPostBackControl method of ScriptManager in PageLoad event for every event raiser controls that exist inside UpdatePanel.

First solution seems be ok but it causes some side effects!
IE 10 specific CSS 3 rules, do not affect on html elements when Document Mode set to IE9.

Second solution is applicable when there are some few event raiser controls inside UpdatePanel.
Because developers should write registration code for each event raiser control, it is not a proper fix method.

I remember, before releasing Internet Explorer 10, there were no errors and problems on Ajaxified Web Applications on IE 6-9.
Please fix this incompatibility problem between "Microsoft AJAX Client Library 4.5" and "Internet Explorer 10+".

I create and attach an application to show this situation.

I am using these tools:
- Windows 8 x64 Enterprise 6.2.9200 + all update packages (from first to Oct 2013)
- Internet Explorer 10.0.9200.16721 (10.0.10) + all update packages (from first to Oct 2013)
- Visual Studio 2012 Ultimate + Update 1
- .NET Framework 4.5 + all update packages (from first to Oct 2013)
Sign in to post a comment.
Posted by Parsa.Laylazi on 10/23/2013 at 6:38 AM
Thanks to your attention.
I run Products.aspx page in last uploaded file (SampleSolution.zip).
Requested data has been collected as new attachment (Product.aspx.Running.Steps.zip).
Please extract it and look at Product.aspx.Running.Steps\Index.html.
Posted by Microsoft on 10/22/2013 at 3:38 PM
Thank you for submitting the issue that you are seeing. Unfortunately, we are not able to reproduct this issue in our labs even with the repro that you attached. Would it be possible for you to:

1. Tell us what error you see in debug mode and release mode (by setting the debug attribute on the compilation node to false or true in web.config)

2. Use the IE F12 debugger tools or the Fiddler Http Debugger to send us the payload you are seeing being sent to the server and received from the server

3. Do send us any javascript call stacks that you are seeing as well

Thanks!
Posted by Microsoft on 10/16/2013 at 3:30 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 10/15/2013 at 5:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)