Force page to open in Internet explorer (Not edge/spartan) - html

<!DOCTYPE HTML>
<html>
<head>
<!-- Mimic Internet Explorer 7 -->
<meta http-equiv="X-UA-Compatible" content="IE=IE8" />
<title>Plania 7.3 Redirector</title>
</head>
<body>
<p>Content goes here.</p>
<meta HTTP-EQUIV="REFRESH" content="5; url=/PlaniaWS/LoginPage.aspx">
</body>
</html>
My Company has a old web Product where the old Version requires Internet Explorer 8.
Using compatebility worked just fine, but With Windows 10 and Edge(Spartan) this no longer Works.
I have noticed other pages are able to make Edge(Spartan) generate the following Message to the user.
How do you make that happen?
I have tried:
<!DOCTYPE HTML>
<html>
<head>
<!-- Mimic Internet Explorer 7 -->
<meta http-equiv="X-UA-Compatible" content="IE=IE8" />
<title>Plania 7.3 Redirector</title>
</head>
<body>
<p>Content goes here.</p>
</body>
</html>
Screenshot of the "error Message" that Edge(spartan) can give users.
EDIT:
Im aware the this is not a good long term solution, the New Version of the Product does not have any browser dependency. But i want to provide support for the old Version so it Works With updates OS.

It might be impossible before, but it is possible now with IE 11.
The answer is using Enterprise mode for IE11. I believe you find all you need from here:
Use Enterprise Mode to improve compatibility
There are two versions of Enterprise Mode schema (v.1 and v.2), it is recommended to use v.2 as suggested by here.
Below is something not easy to be found:
Make Enterprise mode for IE11 work on Windows 7
Current latest version of IE11 on Windows 7 is
version 11.0.9600.17483 (update version 11.0.20)
To make that IE11 work with Enterprise mode , you must install at least cumulative update - KB3160005 for Windows 7.
Open all intranet sites with IE
You forward all intranet over to IE, by enabling this policy:
Administrative Templates\Windows Components\Microsoft Edge\Sends all intranet traffic over to Internet Explorer
This feature works when you input http://site-name format in Edge address bar.
Note: After testing, if URL includes domain name, like http://site-name.contoso.com, Edge will open the site inside itself.

Related

document.body.innerHTML fails on IE when setting it to "<P><HR>"

Our application uses embedded IE control, and we noticed that setting:
document.body.innerHTML it to <P><HR> causes an OLE exception "Unknown runtime error".
I could reproduce this in the IE browser itself (IE version 8).
<!DOCTYPE HTML>
<html>
<head>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title>Untitled</title>
<script>
function load(){
// alert(document.body.innerHTML)
document.body.innerHTML = '<P><HR>';
}
</script>
</head>
<body onload="load()">
</body>
</html>
If the body.innerHTML is set to <P></P><HR> all is good. but the problem that the HTML strings are coming from a DB. Why is this happening and how can this be fixed?
EDIT: The code works fine on IE11. but the problem exists on systems with IE8. no matter if I change FEATURE_CONTROL_BROWSER_EMULATION key. Is there anything could be done for IE8?
The MSIE WBC (Web browser control), whether hosted by a Delphi or .net desktop application use IE7 Emulation by default.... To determine which IE emulation mode your hosted WBC is using add the following snippet to the onload event.
alert(document.documentMode?document.documentMode:'n/a');
To make your WBC use the IE emulation mode you need to add a registry entry in the FEATURE_CONTROL_BROWSER_EMULATION key in the registry.
see the documentation here - https://msdn.microsoft.com/en-us/library/ms537184%28v=vs.85%29.aspx
to get your invalid markup to work.
1. use a valid document type declaration. ().
2. change your FEATURE_CONTROL_BROWSER_EMULATION value in the registry to emulate IE8 or higher....
Ideally you want your WBC to emulate IE11 and modern web standards for html5, but that may not be possible if your existing markup is pre-HTML5,CSS 3.(viz: your markup was developed for IE6 on an intranet website, using DHTML (the early MS versions of HTML).

IE11 browser showing document mode as 5(default)

Im using bootstrap framework and using the follwoing docttype and meta tag.
<!DOCTYPE html>
<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
Here IE showing document mode as 5(default), mean while all the UI got disturbed, any solution for showing IE=edge.
Thanks
Your IE options are probably set to display Intranet sites in Compatibility View. I tested IE 11 at the official Bootstrap site and it was set to Edge using X-UA meta tag.
From the MS documentation:
Via intranet compatibility settings: The "Display intranet sites in Compatibility View" box is checked in the Compatibility View settings."

IE 11 Browser and Major Version change and Meta tags

I'm working on an ASP.NET website. I have a function where I detect the Browser Name and Version to redirect old browsers to an unsupported website.
I'm using the HttpContext.Current.Request.Browser to pull out the 'Browser' and 'MajorVersion' from it.
When I run it from Visual Studio and it runs locally, Internet Explorer 11 comes in as
Browser: internetexplorer
MajorVersion: 11
But when I publish it out to our server, it comes in as
Browser: ie
MajorVersion: 7
All of my layout pages used by the individual razor views have the meta tag:
<meta http-equiv="x-ua-compatible" content="IE=edge" />
I don't know why it comes in as a different Browser when I publish this to our dev servers and works fine when running it locally.
The other thing, when I F12 in Internet Explorer, the Compatibility Mode is 7. This changes on its own.
Any ideas on how to resolve it.
If it helps, I've added these tags to the web.config files too in the project to include these meta tags.
Thanks!

IE9: Force IE9 browser mode and document mode

In IE9, my webpage is displaying as Browser Mode: IE9 Compat View and Document Mode: IE standards, which is breaking all my canvases.
I have made sure to have <!DOCTYPE html> as the very first line.
How can I force "normal" IE9 mode on IE9?
There is the "edge" mode.
<html>
<head>
<title>My Web Page</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
</head>
<body>
<p>Content goes here.</p>
</body>
</html>
From the linked MSDN page:
Edge mode tells Windows Internet Explorer to display content in the
highest mode available, which actually breaks the “lock-in” paradigm.
With Internet Explorer 8, this is equivalent to IE8 mode. If a
(hypothetical) future release of Internet Explorer supported a higher
compatibility mode, pages set to Edge mode would appear in the highest
mode supported by that version; however, those same pages would still
appear in IE8 mode when viewed with Internet Explorer 8.
However, "edge" mode is not encouraged in production use:
It is recommended that Web developers restrict their use of Edge mode to test pages and other non-production uses because of the possible unexpected results of rendering page content in future versions of Windows Internet Explorer.
The following line, taken from HTML5 boilerplate, did the job:
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

Force "Internet Explorer 8" browser mode in intranet

There are "Internet Explorer 8", "Internet Explorer 8 Compatibility Mode", and IE7 mode in IE8.
However, the default setting in IE make all intranet website use "IE8 Compatibility Mode" even I have setted doctype, the meta tag, http header as suggested to force it into IE8 mode.
I have
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
and
<meta http-equiv="X-UA-Compatible" content="IE=8" >
But it still goes into "IE8 Compatibility Mode", without any changes in IE setting.
How to force it into pure "IE8" mode, without change any browser's setting?
PS. I am not talking "document mode" here.
Seem that MSFT has not consider a large intranet environment that we have many different web application running inside.
There is no way to bypass the IE8 setting, according to somewhere I read on MSDN forum.
So, I will have to beg my system administrators to put some new group policies to change "Compatibility View" setting and the value and prevent user change the value, until MSFT discover this bug and fix it.
From an MSDN blog post (emphasis theirs): "Browser Mode is chosen before IE requests web content. This means that sites cannot choose a Browser Mode."
It is possible to override the compatibility mode in intranet. Just add the below code to the web.config. Worked for me with IE9.
<system.webServer>
<httpProtocol>
<customHeaders>
<clear />
<add name="X-UA-Compatible" value="IE=edge" />
</customHeaders>
</httpProtocol>
You'll have to make some adjustments to IE.
Here they are.....
In Internet Options / Local Intranet / Sites
Under : Local Intranet inside Sites, uncheck "Automatically detect intranet network".
Then select only "Include all network paths (UNCs)
See attached screenshots
I found the answers here hard to follow, so here's the important information in a nutshell:
If your intranet uses default settings for IE, IE7 Standards Mode is enforced for intranet sites regardless of any website settings.
From this:
Compatibility View and the Enterprise
A large number of line-of-business
websites are Internet Explorer 7
capable today. In order to preserve
compatibility, Internet Explorer 8
ships with smart defaults based on
zone evaluation. In the default state,
all sites on the public internet
display in Internet Explorer 8
Standards mode (Compatibility View
off) and all intranet websites
display in Internet Explorer 7
Standards mode (Compatibility View
on).
Let’s look at some examples. If you
navigate to sites on your local
intranet like http://myPortal and
http://sharepoint/sites/mySite,
Internet Explorer 8 identifies itself with a User Agent string of
‘7’, Version Vector of ‘7’, and
displays webpages that trigger
standards mode in Internet Explorer 7
Standards mode. This combination
allows webpages that worked correctly
in Internet Explorer 7 to continue to
do so in IE8.
To override the Compatibility View settings for intranet or all websites you need to make IE8 emulate itself.
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" >
Set a custom HTTP header instead of using the <meta... in the <head> section. These are supposed to be equivalent, but I have seen that an X-UA-Compatible HTTP header from the server will override IE 8's "Display intranet sites in Compatibility View" setting, where the <meta... element would not.
If you are using .NET, I have the answer for you:
HTML:
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="X-UA-Compatible" content="IE=8" >
Web.Config:
<system.webServer>
<httpProtocol>
<customHeaders>
<clear />
<add name="X-UA-Compatible" value="IE=8" />
</customHeaders>
</httpProtocol>
Read somewhere that the DOCTYPE declaration must be the very first line. No comments of any kind, nor empty lines.
In combination with setting the HTTP Response Headers, this worked for me. Browser Mode went from "IE9 Compatibility Mode" to just "IE9 Mode".
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\BrowserEmulation
IntranetCompatibilityMode 1-->0
In order for the META declaration to work, the doctype has to be the simplified version:
<!DOCTYPE html>
Not the longer statement in Dennis' question.
This combo did the trick for me:
<!DOCTYPE HTML>
<HEAD>
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" >
</HEAD>
at least IE developer tools reports IE9 Compat View, IE8 standards
just for kicks i tried EmulateIE7 and that worked as well.
simplifying the extended !DOCTYPE was key.
You need remove port number from your domain site name
site:1180/index/
If browser see port number in url - hi "think", that's is intranet.
setup your dns server for friendly urls - site.com/index and it work OK
The answer marked as "correct" is technically correct but suggests that there is no solution to the real issue being faced by most people that is: "how do I properly show on IE8, with compatibility mode enabled, a web application which does not support compatibility mode?".
<!DOCTYPE HTML>
<HEAD>
<meta http-equiv="X-UA-Compatible" content="Edge" >
</HEAD>
this worked for me on several workstations.
If the above code is implemented on application side, IE8 appears to behave as if it was not in compatibility mode, even though it will still show browser mode as compatibility mode.