Usually when I see property errors in IE browsers during debugging I always check the compatibility is off or I check the Browser Mode and DOM mode is the latest for the browser. What I find is somehow it switches for one reason or another to an earlier version. Not sure this is an issue but something easy to check.
On Saturday, October 4, 2014 9:43:15 AM UTC-7, Jens wrote:
-- On Saturday, October 4, 2014 9:43:15 AM UTC-7, Jens wrote:
My suspicion is still that regardless of IE10 or 11 somehow its being run in compatibility mode, which if thats IE8 would explain problems with Trim().We only have the typical <!DOCTYPE html> at the top of our host page which puts all browsers in standards mode. The only way to get IE into compatibility mode then is to either click the corresponding icon in the browser or add the URL to the compatibility view list in IE settings (http://i.msdn.microsoft.com/dynimg/IC488476.png ). We have our load balancers configured to serve a special page if a "compatibility view" user-agent is detected.
Also IE 11 might require IE 10 mode if your app has errors in IE 11 while executing the Firefox permutation. In that case you would add <meta http-equiv="X-UA-Compatible" content="IE=10"> to your head and file a bug on GWT to fix the issue.-- J.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment