Might anyone know why DD_belatedPNG works wonders for my transparent pngs in IE6 and IE7, but not in IE8?
Thanks.
You can also use the content attribute to specify multiple document compatibility modes. To specify multiple document modes, set the content attribute to identify the modes you want to use. Use a comma to separate each mode.
If a particular version of Internet Explorer supports more than one requested compatibility mode, it will use the highest available mode listed in the content attribute. You can use this fact to exclude specific compatibility modes, although this is not recommended. For example, the following header excludes IE7 mode.
<meta http-equiv="X-UA-Compatible" content="IE=9; IE=7;" >
This should force IE8 to run like IE7 and IE9 to stay as IE9
Source: http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx
According to this blog, you have to use a X-UA-Compatible meta tag for it to "work".
Related
When I am trying to upload a file using ieframe in IE9<, am getting the error in developer tools:
HTML1113: Document mode restart from IE9 Standards to Quirks
Hence the upload status is not displayed. I tried using meta tag <meta http-equiv="X-UA-Compatible" content="IE=8"> but it's still not working.
Can any one throw some light on it.
According the IE11 console error reference:
"HTML1113: Document mode restart from [mode] to [mode]
The webpage requires a different document mode than the browser was
currently set to.
This message can occur when the user browses from another page, so it can be out of the developer's control."
Given your description, it sounds like your child frame is embedded within a larger document. If that's the case, verify that the document modes of both document are consistent. If one requires standards mode, the other should be using it as well.
For best results, use the HTML5 doctype (<!DOCTYPE html>) for all documents; this will trigger standards mode (or edge mode, as it's now called) in each version of IE. If you're not able to do this, then you may wish to try opening the framed document in a new window, rather than embedding it on a parent document.
Hope this helps...
-- Lance
Here is the doctype I am using:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
This will happen if you have content (an HTML comment perhaps) before the DOCTYPE. White-space should be OK in IE8 - although I think even this caused problems with IE6.
(In IE6 an XML declaration before the DOCTYPE would trigger quirks mode - this was fixed in IE7, but it would seem that other content before the DOCTYPE still triggers this.)
not being funny, and I'm sure you've already checked this, but...
Have you tried pressing F12 to step into the IE Developer Console. Is there achance maybe that the "Document Mode" or "Browser Mode" is set to "Quirks Mode"
Forgive me if this isn't the case... I've simply fallen foul of this stupidity before...
It sounds like you're dealing with an Intranet page, which IE8 and IE9 treat differently. If your page is considered to be in the Intranet Zone, IE8 will default to a compatibility mode that might be borking your page up a bit.
You may be able to get around this by using the X-UA-Compatible meta element, but I haven't tested this myself.
This page is high in Google rankings for 'why page triggers ie8 quirks mode', so I will post my 2 findings (through painfull troubleshooting experience):
1) Page will triger quirks mode if you use php in general, but say on that particular page you do not have any php code in the before <html> section at all, but for compatibility you wish to write empty <?php ?> tags at the opening. Now, say, you wish to 'minimize' that code and remove all the empty spaces in between, so you write:
<?php?>
This will trigger IE8 Quirks Mode, because before <!DOCTYPE html> now you will have an extra line with something like this in IE8:
<!-- -->
and in Chrome 34.x:
<!--?php?-->
common, but deadly mistake. Just put
<?php ?>
(with space) to be safe.
2) Second reason was indeed very hard to discover. If you use UTF-8 for your documents and edit them with Notepad++, you will most probably set your character encoding as pure UTF-8 (Notepad++ > Encoding > Encode in UTF-8), and by chance you may trigger IE8 Quirks Mode!
Now, the solution is very simple: using Notepad++ just select Encoding > Convert using UTF-8 without BOM.
Quirks Mode is again gone!
Took me a while to catch all these, trying hard to find bugs in CSS, that were not CSS-related at all!
I'm running Selenium in singleWindow mode and IE8.
If i start IE8 manually the IE8 mode is set, but when i launch it with Selenium, the mode set is IE7 using the compatibility mode.
Anyone knows why the compatibility mode is not the IE8 view when launching the browser with Selenium?
Or, how can i disable totally the compatibility mode in IE and force it to use always the IE8 view?
I've given the question a +1 because it's a very good question -- it's not obvious how to do this, and if you need to test both modes, then it is a necessary thing to do.
You could get the site to serve <meta http-equiv="X-UA-Compatible" content="IE=7" /> within the page when running the tests. This should force the output mode.
Obviously, that's not ideal, because it means changing your code to produce the meta tag on demand. I'd normally consider it a bad thing if you're having to change the main codebase in to add code for the specific use of your test suite, but in this case I can't see any other solution.
Given that we've decided to go down this path, you could write your code to accept a specified argument in the URL that triggers the meta tag to be served. The IE7 tests could then be written to send that URL argument.
By the way, it's worth pointing out that IE8's IE7-compatibility mode is not 100% identical to IE7; it has its own quirks and bugs which are distinct from those of a real IE7 browser. For the most part it should be fine, but it's worth being aware of this if you're expecting your tests to confirm that the site works in IE7. See this blog post for more info
I have some workarond solution for this, I use it regularly:
In internet explorer goto:
1. Tools / Compatibility view settings.
2. At the Add website input textbox add your website url.
Hope that helps, best regards,
Peter Nadasi (HUN)
I have a problem I haven't seen before. I am doing a realign on our company's website and am testing locally. However, when I upload to our test server I notice display discrepancies within the same browser (IE8)!
Here is a screenshot of the two pages, both viewed in IE8 but residing on different servers. In the page on the right, you can see there is a weird chunk of white space to the side underneath the .swf file.
Can anyone give any insight as to why the same page on distinct servers would look different in the same browser? I have also noticed a couple of other cross-server bugs within Firefox.
Thanks!
One possibility that comes to mind is IE8's compatibility mode. There is the X-UA-Compatible header directive that forces IE8 into compatibility mode or out of it. Maybe one of the servers sends out that information.
Try adding a compatibility mode directive to the header and see whether it has any effect:
<!-- Mimic Internet Explorer 7 -->
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" >
and alternatively:
<meta http-equiv="X-UA-Compatible" content="IE=100" > <!-- IE8 mode -->
Reference at MSDN: Defining Document Compatibility
One of our products uses a Javascript Rich text editor, which has the ability to accept pasted HTML/Word and clean it up so the html is XHtml valid and presentable.
This has been working fine for a few years, but recently we've been having complaints about pasting; from users with IE8.
It turns out that regardless of setting the group policy setting for allowing pasting, or prompt for pasting; if IE8 mode is enabled, it won't paste.
If you turn on compatibility mode, it works correctly, but we'd like to have a solution that works across the board.
Has anyone had this issue or similar ?
Unfortunately, we deal with a lot of corporate/local goverment entities that don't have the flexibility to change their browser/policies without submission through strict change-request red-tape :(
Thanks for any insight!
If you aren't worried about formatted text then try the clipBoardData object. It's not ideal but its about the only thing that works other than running in compatibility mode via the web developer tools.
Not a solution, but could you use the <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> meta-tag to force compatibility-mode for IE8 users?
I think some intranet group policy settings may override that and it's a sticking plaster rather than a solution, but it may get you by while you find a proper fix.