I am currently running IE in edgemode but only when I use the devtools(F12). When I turn off the devtools it seems to be running in IE 7 mode. How can I change this without adjusting the registry? I am not an admin on this machine I am working on.
you can use Meta tag:
<html>
<head>
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<title>My Web Page</title>
</head>
<body>
<p>Content goes here.</p>
</body>
</html>
Either you can use Enterprise Mode Site List Manager
2.1 Use Enterprise Mode to improve compatibility
2.2 Fix web compatibility issues using document modes and the Enterprise Mode site list
Thanks :-)
Related
I have problem with CKEditor. I download lastest version and implement on my CMS. All buttons and textarea are disabled and I can't do anything. I searched and find solutions like CKEditor.inline or readOnly but it just doesn't work...
My code looks just like:
<!DOCTYPE HTML>
<html lang="pl">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Test</title>
<script type="text/javascript" src="ckeditor/ckeditor.js"></script>
</head>
<body>
<textarea name="editor" class="text" rows="4" cols="115">Some text</textarea>
<script type="text/javascript">
CKEDITOR.replace("editor");
</script>
</body>
</html>
And here is live version: http://www.hbmedia.pl/test.php
I finally figured this one out. Thought I'd post an answer in case anybody else comes across this question.
In order for the "Classic Editor" to function within a custom ckeditor4 package, you need to make sure the "wysiwygarea" feature is added to the package. This is named "iFrame editing area" in the feature list.
If you don't do this, only the inline editor is available, even though the classic editor shows up as disabled.
If you don't want to use iframe as a content container you might want to use Div editing area. The behaviour is described in IFrame Editing Area page in the notes section:
This is the core functionality of the classic, iframe-based editor which can only be disabled if it is backfilled by an alternative plugin (such as Div Editing Area) or if only inline editor is used.
I downloaded and deployed the 2 AngularJS demos below
https://code.msdn.microsoft.com/windowsapps/AngularJS-TODO-Sample-for-b651512a
https://code.msdn.microsoft.com/AngularJS-Detail-Sample-7a409e5e/view/Discussions
I deployed them to WP8 and Android devices and they worked fine.
But when I deployed to Windows 8 Store App, the input box does not work.
Both demos have the same issues.
I tried using VS 2013 and VS 2015. The outcomes are the same.
Am I missing any build setting? Please advice.
I searched this few days. Add:
ng-csp
to html tag:
<!DOCTYPE html>
<html ng-csp>
<head>
<meta charset="utf-8" />
<title>BlankCordovaApp1</title>
<!-- BlankCordovaApp1 references -->
<link href="css/index.css" rel="stylesheet" />
<!-- Cordova reference, this is added to your app when it's built. -->
<script src="cordova.js"></script>
<script src="scripts/platformOverrides.js"></script>
<script src="scripts/angular.js"></script>
<script src="scripts/index.js"></script>
</head>
<body ng-app="">
<p>Hello, your application is ready!</p>
<input type="text" value="text" />
</body>
</html>
Please refer to my stackoverflow response for a similar problem.
There are a few things you may want to check in your app - the version of jQuery should be >= 2.x, ng-cspis added to your index.html and winstore-jscompatlibrary is added to your project.
These are common issues that windows 8.1 apps with angularjs/jQuery throw. Hope this helps!
My Application is compatible only with IE8.So, whenever we open the page,Broswer Mode should set automatically to IE 8,instead of going to developer tools and setting there
I always use
<meta http-equiv="x-ua-compatible" content="IE=EmulateIE8" >
this needs to get in the head tag.
You need to add a meta tag to your document head specifying IE8 compatibility mode.
<meta http-equiv="x-ua-compatible" content="IE=8" >
My document looks like this:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<!--[if lte IE 8]>
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
<![endif]-->
I'm using IE10 to test everything. When I switch Browser Mode to IE7 the Page Default Document Mode shows to be IE7 standards. However when I switch to IE8 Browser Mode the Page Default Document Mode is IE8 standards. Why doesn't the meta tag change it to IE7 standards? Is it something to do with my browser configuration? How can I make sure that everyone who look at my site from IE8 get the Document Mode of IE7 by default?
You're hiding the meta tag, so IE10 will never see it. You'll need to remove the conditional comment wrapping.
And then, I presume that when you put IE in IE8 browser mode, that action forces use of the IE8 renderer and thus it will ignore the X-UA-Compatible header.
I'm apparently triggering quirks mode (or at least IE 7 standards mode) even though I've added the strict doctype:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
and the IE compatibility list meta:
<meta http-equiv="X-UA-Compatible" content="IE=8" />
I've looked at the Developer Tools window for the page, and it says that the page default is IE 8 standards mode, but still renders the page wrongly. However, changing the mode in developer tools to another mode and then switching back to IE 8 standards mode causes the page to render correctly.
Is there some other IE-specific incantation that I'm missing, or is this a known bug for IE 8 (or the IE Developer Tools)?
If it helps, here are the first few lines of the page (Sorry I don't have a link to the page, it's a proprietary product that is intended for deployment on intranets). I've checked that nothing comes before the DOCTYPE (though that apparently is no longer an issue for IE 8):
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<!-- to override ie compatibility mode for intranets: http://blogs.msdn.com/b/ie/archive/2009/02/16/just-the-facts-recap-of-compatibility-view.aspx -->
<meta http-equiv="X-UA-Compatible" content="IE=8" />
Either change your DOCTYPE to an XHTML one, or remove your self-closing tags.
I have encountered identical problem as Neil Ongkingco described. We've added a DOCTYPE, and the developer tool shows that the IE is rendering in IE8 Standard Mode. However, the webpage do not render as we expected. Changing the mode back and forth fixes the problem for that session, but it's not working as described. Here is what we've done to fix the problem.
We kept the DOCTYPE as below. I don't think it matters whether you have Loose or Strict mode.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
Added the X-UA-Compatible metatag as described. We left out the closing slash as shown below.
<meta http-equiv="X-UA-Compatible" content="IE=8">