quirks-mode

How do I get IE9 to use standards compliant mode when developing on localhost?

北城以北 提交于 2019-11-30 00:36:39
问题 According to MSDN, all I need to force standards compliant mode is to include the HTML 5 doctype: http://msdn.microsoft.com/en-us/library/gg699338%28v=vs.85%29.aspx And it works when the markup is served remotely. The problem is when I take identical markup and serve it up from an apache server running locally. IE9 defaults to quirks mode, and the compatibility view button goes away. I do a lot of development locally, and it defeats the purpose if I can only test my code in IE when it's

Doctype and Quirk modes and HTML 5

独自空忆成欢 提交于 2019-11-29 17:25:58
I am having quite a horrible time. We have a massive site that has no <DOCTYPE> and when I run it with IE10 it goes into quirks mode and after some CSS changes looks ok. As soon as I add echo "<!DOCTYPE HTML>"; The complete site looks terrible and the CSS is not looking as it suppose to. It turns the browser mode to IE10 and docmode to standard. Is there a way to keep HTML 5 functionality but use IE5 Quirks mode or just Quirks mode so the CSS will look correct? No. The whole point of quirks mode is that it's a compatibility mode for IE5. This means that in addition to changing the layout mode,

IE 10's -ms-clear pseudo-element, and IE5 quirks mode

瘦欲@ 提交于 2019-11-29 14:46:22
问题 I'm working on a legacy web app that requires use of Internet Explorer's 'IE5 Quirks Mode' (set using X-UA-Compatible: IE=5 ). A number of text fields in the app have (app-generated) 'x' buttons to clear the content. In IE10, IE also generates an 'x' button to clear the field, so the user sees two of them. As discussed in this question, you can remove the IE-generated 'x' using the ::-ms-clear CSS pseudo-element. Unfortunately, this appears not to work in IE5 Quirks Mode: styling of the ::-ms

Can an iframe content be rendered in standards mode when the parent is rendered in Quirks mode?

徘徊边缘 提交于 2019-11-29 14:44:32
I have an html page which renders an html page in an iframe where my page adds a topbar to the whole content. Inorder to render the whole page seemless, I had to rely on quirksmode rendering of the page to display the following:(similar to the way google image results page(page u get on click of an image with a top frame)- <table> <tbody> <tr> <td> <!-- Top bar content --> </td> </tr> <tr> <td> <iframe src="http://anysite.com/"/> </td> </tr> </tbody> </table> The problem here is that there are pages which donot render properly in quirks mode. So they do not come out properly in the iframe. How

IE8 bug in for-in JavaScript statement?

醉酒当歌 提交于 2019-11-29 13:49:36
问题 I think I've found a bug in IE's (IE8) handling for the for-in javascript statement. After several hours of boiling this down to a small example, it looks like IE specifically skips any property called "toString" in a for-in loop - regardless of whether it is in a prototype or is an "Own Property" of the object. I've placed my test code here: function countProps(obj) { var c = 0; for (var prop in obj) { c++; } return c; } var obj = { toString: function() { return "hello"; } }; function test()

Dreamweaver causing Quirks Mode in Internet Explorer

馋奶兔 提交于 2019-11-29 11:27:55
I use Dreamweaver to develop Web sites. I use the templates feature extensively as it helps to make things easier maintaining conformance. However, I notice that Dreamweaver adds the following code before the doctype: <!-- InstanceBegin template="/templates/web-public-user-home.dwt" codeOutsideHTMLIsLocked="false" --> This is throwing my IE into Quirks mode for obvious reasons (i.e. comment before the doctype). Is there a way of dealing with this?! Below is my doctype. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

Force IE9 into Quirks mode?

别等时光非礼了梦想. 提交于 2019-11-29 09:11:04
I have a page with an iframe, and the iframe contains code that needs to run in quirks mode (it's Microsoft's Outlook Web Access, so it's not our code that we could fix anyway). IE9 introduced a "feature" that when the parent frame is in IE9 document mode, it also forces any iframes into the same document mode. This breaks the code we have an the iframe. I was hoping this was a bug in IE9, but my ticket was turned down as "by design" ( here is the ticket if you care to look) I can't run the entire site in quirks mode, but I need it to happen only on this page. Is there a way to

Trying to use IE=edge X-UA-Compatible in an iframe on a page using IE=EmulateIE7

余生颓废 提交于 2019-11-28 21:10:14
I have a page that's going to be included in an iframe on a page where they use the following: <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7"/> and ideally I'd like to render my page in using the latest standards mode available to the browser the user is using. Is this possible? I've tried including <meta http-equiv="X-UA-Compatible" content="IE=edge"/> on my page, as well as altering my webapp to include the 'X-UA-Compatible' HTTP header with value of 'IE=edge', but I can't seem to get it to do what I want. The odd thing is, is that if for instance I have two pages, the first

Set element width or height in Standards Mode

℡╲_俬逩灬. 提交于 2019-11-28 17:41:22
Is it possible to set width or height of HTML element (ex. <div> ) in JavaScript in Standards Mode? Note the following code: <html> <script language="javascript" type="text/javascript"> function changeWidth(){ var e1 = document.getElementById("e1"); e1.style.width = 400; } </script> <body> <input type="button" value="change width" onclick="changeWidth()"/> <div id="e1" style="width:20px;height:20px; background-color:#096"></div> </body> </html> When user presses the change width button, the <div> 's width should change. It works fine when doctype declaration determines Quirks Mode. In

Why “XSLT8690: XSLT processing failed” when processing local xml + xslt

爷,独闯天下 提交于 2019-11-28 13:07:12
Extensive research did not lead me to understanding why the below happens - I hope that the SO community can help... I copied the files mentioned in Why HTML1113: Document mode restart from IE9 Standards to Quirks to local filesystem and opened the xml in IE9 (by specifying the path D:\... in the url bar). Surprisingly, the behavior is quite different from opening the web version. Now I can understand that "My Computer" zone settings differing from Internet zone ones explain the pop-up windows mentioned below, but I don't understand why the result is different and why quirks mode is not