So I have a GWT application that works perfectly in IE6-8, and most all modern browsers. Unfortunately, due to a known bug in how IE9 handles onchange events on <select> elements, it's pretty much unusable in IE9.
So instead of having our clients downgrade to IE8, I had the brilliant idea of having IE9 emulate IE8. I put this meta tag in my GWT host page:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" >
When I look at the IE9 Developer Tools (F12), I see that it's "Browser mode" is IE9 and "Document mode" is IE8 standards. The GWT app doesn't load, though: it gives me a JavaScript error in one of the compressed and obfuscated JavaScript functions generated by GWT. I don't have the ability to debug into the app via IE so I can't figure out what's going on that way.
I suspect it has something to do with the way GWT detects which browser is being used and loads the appropriate resources for the session.
Edited to add: When I try to use IE=8 instead of IE=EmulateIE8, Developer Tools still reports a IE9/IE9 standards mode and all of the same onchange event issues are present as when I run in vanilla IE9.
Is there a working way to make IE9 emulate IE8 Standards mode in the way the http-equiv meta tag does, that works with GWT 2.4?
I've had similar problem: IE ignored <meta http-equiv="X-UA-Compatible" content="IE=9"> tag (I was trying to prevent IE8 from displaying the page in IE7 compat mode). It was caused by not having X-UA-Compatible meta as the first child of <head>. I set it as the first child of <head> and added <!DOCTYPE HTML> on top of everything, and it worked.
Related
I am confused... all the pages start with
<!DOCTYPE html>
<html lang="en">
<head>
<title>...
When I view the source in Firefox, the first line is in italic. Is it commented by FF (last mac version 98.0.1)?
In the web tools console, FF sometimes (not for all the pages) displays a warning saying that the page is in quirk mode and may affect the rendering.
I have read a lot on the subject but I don't seem to understand what I can do to fix this.
Help would be appreciated.
Is it possible for you to inject an iframe without the doctype or for some third party tracking pixel to do it?
If that's the case, I'm afraid your problem is caused by that, you have an answer to the reason here:
Dynamic iframe inserted into document that is standards mode defaults to quirks mode
I am a new user to fancybox 2.0 and have to been able to get it to work. After a couple of days trying, I eventually stripped down test page do the bare bones. It works with Firefox but not with IE8.
Please, can someone look at this code and see where I am going wrong.
http://www.bytebrothers.com/bb_tester/Video_lightbox_test.htm
Your document has not DOCTYPE so IE switches to quirks mode.
Fancybox needs standards mode to run properly so set a valid DOCTYPE. You can check http://www.alistapart.com/articles/doctype/ or simply set <!DOCTYPE html>
I am using the latest version of TinyMCE which will render in IE9 but I cannot interact with it.
Removing document.domain will allow it work again, but I need document.domain to make the popup windows in tinyMCE work in my setup.
I have tried using <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> and such but this doesn't seem to make any difference.
I'm creating an application using GWT 2.0.1; it complies 6 computations and runs well in all browsers except IE8, it shows a blank page( but can be viewed in IE8 compatibility mode) .
When I add the line in my gwt.xml
<set-property name="user.agent" value="ie8" / >
it compiles just 1 permutation and the application displays fine in IE8. However if I add the line
<set-property name="user.agent" value="ie8,gecko,gecko1_8,safari,opera" />
it compiles all permutations, but the application still cannot be viewed in IE8 but runs properly in all other browsers.
Is there any other method to ensure my application will run in all browsers ?
According to this page besides setting the proper user agent you have to add the following meta tag to enforce IE8 standards mode:
<meta http-equiv="X-UA-Compatible" content="IE=8"/>
For those who are looking for a nice solution, you have to insert this line :
<meta http-equiv="X-UA-Compatible" content="IE=5,6,8,9" >
in your .html file (the host page)
This will ensure that your page is compatible with ascendant IEs...
I had a similar issue once and the problem was that the HTML page that bootstrapped the GWT JavaScript had an unmatched HTML tag. This didn't cause a problem in Firefox or Chrome, but IE just displayed a blank page. Try verifying your HTML using an HTML Validator. The W3C validator is a the cannonical service.
http://validator.w3.org/
instead of
<set-property name="user.agent" value="ie8,gecko,gecko1_8,safari,opera" / >
Try diffing the generated permutations for IE8 when you use <set-property name="user.agent" value="ie8" / > and when you use <set-property name="user.agent" value="ie8,gecko,gecko1_8,safari,opera" />. If they are different, you might get some clue to take forward your investigation. Use fiddler or IE developer tools to monitor and compare the names of *.cache.js files being loaded in each case.
Update: Please disregard, my problem was caused by an advertisement bar being inserted by the vendor who provides my workplace wireless service.
I was building a mobile friendly website and wanted to use HTML 5. However when I specify the doctype as <!DOCTYPE HTML> , I get a gap at the top of the page on safari on the iphone.
I notice that other sites have the same problem such as nextstop.com and nike.com
I guess safari does not fully support HTML 5 yet. Anybody know of a workaround?
HTML 5 is still in a very unstable state. Don't use it in a production environment.
Edit Just so you guys know what it's about, HTML 5 is currently an Editor's Draft, and the document clearly states (in the Status of This Document section) that this specification is not stable, and that a consensus may not have been reached on any of the proposed sections. I think it should be clear enough that it means it's a bit early to start using it.
All browsers correctly interpret the HTML doctype. Putting it in sets your browser into Standards Compliant mode, that is the only difference with or without the doctype.
You can use a CSS reset tool like http://meyerweb.com/eric/tools/css/reset/ to get rid of default margins and padding on all elements.