Till IE9, my application was working fine with compatibility mode on. Now our uses are being upgraded to IE11 but it seems IE11 doesn't have option to view the page in compatibility mode. Compatibility view setting in IE11 is adding the whole intranet domain which I don't want as few local websites are expecting this setting to off.
http:\\intranet.xxxx.com\XXXX\YYYY - Application 1
http:\\intranet.xxxx.com\AAAA\BBBB - Application 2
With IE11, my UI is not rendering properly due to css issues. I tried below tag but it also not working. Is there any way either code, web server config or simple client side setting to run the individual website in compaitibility mode.
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
Thanks.
If they worked in IE9's compatibility mode, have you tried this?
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
or
<meta http-equiv="X-UA-Compatible" content="IE=7" />
Related
I have a main application, made with Microsoft .NET Framework 4.7 (MVC) that is forced (and must) to run with Compatibility Mode IE11.
Inside that application, there is a specific page with a iFrame that run a .Net Framework 1.1 application that must run in Compatibility Mode IE7.
The problem is that both (main and iframe) are running with compatibility mode IE11 and, because of that, frame application doesn't run properly.
At the moment, I've already tried to force iframe application to run in IE7 by adding to the IIS HTTP Headers the following pair key-value:
Custom header name: 'X-UA-Compatible'
Custom header valuebox: 'IE=EmulateIE7'
However it didn't solve my problem and i am out of ideas now.
Any suggestion?
Thank you in advance!
I think you should you meta tags to specify the compatibility mode (not sure if the http header do the same thing). According to this answer it should be posible:
Main web page in standard mode, iframe in compatibility mode: any issues?
Here is quite thorough documentation of what are the options:
What does <meta http-equiv="X-UA-Compatible" content="IE=edge"> do?
Please check this similar thread, try to use the IE browser Quirks Mode.
In the iframe content page, omit Doctype and add
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
I am working on a project that the client only allows their employers to look at intranet site. Therefore, in my project IE11 defaults to compatibility mode for intranet sites. Meta tag <meta http-equiv="X-UA-Compatible" content="IE=edge"> gets overwritten. How do we set the content="IE=edge" even on intranet sites?
After searching for an answer, my co-worker helped solved this problem in Ruby. I research why IE11 was ignoring:
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
The setting for IE=Edge has to render on the response header. This post Force IE compatibility mode off using tags helped lead to an answer.
In your project find your controller that sets up your headers. In our project it is application_controller.rb.
Add:
before_filter :set_default_headers
def set_default_headers
response.headers["X-UA-Compatible"] = "IE=edge"
end
This will allow IE11 to view the page in Edge even when the site is rendering for intranet view.
I have an MVC development which works fine when run locally. When deployed to an Azure Web Site, I'm seeing the same results (as expected) in Firefox, Chrome, IE8, and others. When viewed in IE11 (the same browser that I'm using to view the site locally), the layout is all over the place.
It seems that when Azure Web Sites renders the site, the IE11 browser is dropping into "7 (Default)" Document Mode. Pressing F12 and resetting to Edge gets the rendering back to how it should be.
I'm struggling to work out what is going on in Azure Web Sites that is causing this behaviour. I'm thinking it's a compatibility setting somewhere and any pointers would be appreciated.
Thanks, Nick.
As explained by #ahmelsayed above, adding the
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
tag has fixed the problem. Thanks for the support.
Internet Explorer 10 has built in spell checker and it works just fine. I tried to create a small HTML page to test it with following contents:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML lang=en xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><HEAD>
<META name=GENERATOR content="MSHTML 10.00.9200.16721"></HEAD>
<BODY spellcheck=true contentEditable=true style="MARGIN: 0.5em">
<P>Theze ara mispeled wordz</P>
</BODY></HTML>
All that is needed is to put properties spellcheck=true and contentEditable=true.
I also tried adding <meta http-equiv="X-UA-Compatible" content="IE=10" /> e.g.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML lang=en xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><HEAD>
<meta http-equiv="X-UA-Compatible" content="IE=10" />
<META name=GENERATOR content="MSHTML 10.00.9200.16721"></HEAD>
<BODY spellcheck=true contentEditable=true style="MARGIN: 0.5em">
<P>Theze ara mispeled wordz</P>
</BODY></HTML>
For that matter, using IE=edge instead of IE=10 doesn't make any difference:
What does <meta http-equiv="X-UA-Compatible" content="IE=edge"> do?
I then tried adding setting FEATURE_BROWSER_EMULATION to registry:
http://www.west-wind.com/weblog/posts/2011/May/21/Web-Browser-Control-Specifying-the-IE-Version
This improved rendering of certain elements which had CSS styles like border-radius so at least I could see it is in IE10 mode, but still no spell checker.
The above page works in Internet Explorer browser and spell check is working.
However, when same content is loaded into TWebBrowser (I use TEmbeddedWB but it is just the same wrapper anyway) it doesn't work.
After googling and googling for solutions, still haven't found one. Do you know is this even possible in WebBrowser control? I need the solution that would work on Windows 7 not just Windows 8. I've seen the registry entry FEATURE_SPELLCHECKING but it applies only to Windows 8.
Are there any alternative solutions that would work within DesignMode of TWebBrowser control? I am looking for curvy red underline thing like in Word or other programs and possible GUI window to offer alternative words.
I think you are out of luck here.
There was a bug report on Microsoft Connect concerning FEATURE_SPELLCHECKING and windows 7. Unfortunately it has been closed "as Designed".
This is the official answer from Microsoft:
Thank you for your feedback.
After additional review, the spelling feature is only supported on
Windows 8 and higher and is not supported on Windows 7. This is
because the spelling feature was built into the Windows 8 platform.
Best regards,
The Internet Explorer Team
try to change it in the registry...
Bye
Nicolas Perichon
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
SOFTWARE Microsoft Internet Explorer Main FeatureControl
FEATURE_BROWSER_EMULATION
contoso.exe = (DWORD) 000090000
10001 (0x2711)Internet Explorer 10. Webpages are displayed in IE10 Standards mode, regardless of the !DOCTYPE directive.
10000 (0x02710) Internet Explorer 10. Webpages containing standards-based !DOCTYPE directives are displayed in IE10 Standards mode. Default value for Internet Explorer 10.
info de Microsoft:
msdn.microsoft.com/en-us/library/ee330730%28VS.85%29.aspx#browser_emulation
We have deployed our webapp, which was developed with JSF, Spring and Hibernate on Tomcat server in our internal network (intranet). When I test in my application in local it's working fine.
But once I deploy to DEV I come across style issues. When I have two dropdowns one after another, the top dropdown overlaps with another one.
This happens when I have Document Mode set to "IE7 standards." When I change Document Mode to "IE8 standards," everything works fine.
To force Document Mode to IE8 standards, I tried this meta tag in my section of the HTML document according to this link, but it didn't work for me:
<meta http-equiv="X-UA-Compatible" content="IE=edge" >
How can I force my page to render according to IE8 standards on the intranet? Does my application render in IE8 standards on the internet?
EDIT :I see something in my develoer tools.Even though I kept my <meta> it after <head> but my primefaces styles and scripts are loading before to that.How can I resolve this?
Odd, this item was posted yesterday, not sure if it applies to your situation:
IE 8 will ignore the x-ua-compatible setting if it comes after the stylesheets. In order for IE to acknowledge the meta setting, put it at the top.
I am glad to tell I am finally able to resolve this issue by using this link in primefaces.And this post also helped to do it through entire application
http://blog.primefaces.org/?p=1433