Question

197

Force IE 11 User agent string using tags

rated 0 times [ 198] [ 1] / answers: 1 / hits: 34647 / 11 Years ago, thu, november 21, 2013, 12:00:00

My website is broken in IE11.

We all know that HTML tags allow developer to force IE compatibility mode; in example

<meta http-equiv=X-UA-Compatible content=IE=8, IE=9 />

worked great and solved the visualization problems for IE10.

But actually on IE11, even if Compatibility mode is set to IE9, User agent string is set to default and javascript doesn't work.
Changing manually User agent string to IE10 solved my problems.

For shure I'm going to solve the real problems that cause website errors, but actually I need a fast, programatic way to force User agent string to IE10, since I can't contact every user.

Can someone help?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

breonnamayah

Add To Favorites

Follow

Total Points: 574

Total Questions: 115

Total Answers: 96

Location: England

Member since Sun, May 21, 2023

1 Year ago

breonnamayah questions

1 JSX element type 'x' does not have any construct or call signatures

Sun, Nov 14, 21, 00:00, 3 Years ago

1 How do i add items to my cart using javascript?

Sun, Oct 31, 21, 00:00, 3 Years ago

1 How can i get index use forEach loop?

Thu, Jun 3, 21, 00:00, 3 Years ago

1 Unexpected unhandledRejection event for promise which rejection does get handled

Tue, Oct 13, 20, 00:00, 4 Years ago

1 React: How to combine each multiple styles marked in Material-UI

Mon, Mar 16, 20, 00:00, 4 Years ago

View All

answered 11 Years ago soniap · Accepted Answer

Solved! Website is up just installing Dotnet framework 4.5 on server

Actually I didn't find a way to force programmatically browsers User agent string (this was the original question). But repaired website with 0 code..

Just made lot of tests and on one server I found out that website was working, on other server it wasn't.

The good server was a Win2012, and bad servers were Win2008. On Win2012 Aspnet 4.5 was running, and on Win2008 it wasn't.

I installed dotnet framework 4.5 on bad servers too, and everything started working!