Author: j...@google.com
Date: Mon Apr 27 09:25:42 2009
New Revision: 5285
Modified:
wiki/IE8Support.wiki
Log:
Edited wiki page through web user interface.
Modified: wiki/IE8Support.wiki
==============================================================================
--- wiki/IE8Support.wiki (original)
+++ wiki/IE8Support.wiki Mon Apr 27 09:25:42 2009
@@ -13,6 +13,8 @@
While we could *two* user-agent targets (for a total of three: ie6, ie7,
and ie8), this would have a significant impact on compile time, so we're
going to leave "ie6" for both IE6 and IE7 support, and add "ie8" for IE8
and up.
+We also need to ensure that you only get the IE8 deferred-binding if you
are actually in IE8 standards-mode. Even when you're not in "compatibility
view", if there's no DOCTYPE, you are essentially running IE7. MSDN
encourages people to use the document.documentMode property to determine
this, which we can do in the property provider.
+
= Details =
* Modules that need to be updated:
* UserAgent
@@ -56,6 +58,8 @@
= Open Questions =
* How can we force IE8 Standards Mode without requiring a meta tag?
+ * Turns out "compatibility view" reports the user-agent as IE7, which
will use the ie6 deferred-binding. This works fine.
+ * IE8's "normal mode" without a DOCTYPE will give you essentially
compatibility view. We need to detect this with (document.documentMode >=
8), and fall back to the ie6 deferred-binding.
* Should the deferred-binding targets be IE6/7, IE8 -- or IE6, IE7/8?
* Let's go with the former. IE6 and 7 are pretty close to one another,
and IE7 is unlikely to ever change again in a significant way, whereas IE8
probably will.
* Do we still need the ugly IE6/7 StyleInjectorImpl on IE8?
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
