Home Dashboard Directory Help
Search

.NET Browser Compatibility needs to be updated for IE11 by laffer1


Status: 

Closed
 as Fixed Help for as Fixed


2
0
Sign in
to vote
Type: Bug
ID: 802150
Opened: 9/24/2013 2:50:03 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Internet Explorer 11 has a new user agent string and is not detected properly by .NET 4 as supporting async postback, etc.
Details
Sign in to post a comment.
Posted by laffer1 on 10/24/2013 at 4:17 PM
I've been unable to reproduce the original issue with IE11 on Windows 8.1 (release).

We had some success creating a browser caps entry in web.config for the last public beta of IE11/WIndows 8.1 on modern.ie VMs. The ajax related properties were not getting set so the controls would fallback to working without ajax. This was a problem for our specific application as we were using a vendor product and submitting the form from an ajax front end we wrote internally. (see https://leadersandbest.umich.edu/find/ for an example of the app) This was getting fired from the review screen far into checkout.
Posted by The AJ on 10/24/2013 at 9:32 AM
Upon further investigation, our server needs to be updated with KB2836939, which reports to have resolved the user agent string issue I've previously noted.
Posted by The AJ on 10/24/2013 at 8:46 AM
Request.Browser.MajorVersion.ToString produces a ArgumentNullException when the user agent = "Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; Touch; rv:11.0) like Gecko"
Posted by Microsoft on 9/27/2013 at 1:57 AM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested.
Posted by Microsoft on 9/26/2013 at 12:05 AM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested.
Posted by Microsoft on 9/24/2013 at 11:43 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

We look forward to hearing from you with this information.
Posted by Microsoft on 9/24/2013 at 3: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)
Sign in to post a workaround.