Tuesday, October 28, 2014

Re: ie10 permutation causing browser errors? (gwt 2.6.1) really baffled here.

Doesn't solve all the mysteries but until ie11 is correctly supported

" <meta http-equiv="X-UA-Compatible" content="IE=10">" does the job for now....ish

The GWT code loads, but some page elements were using features only supported on ie11 (CSS borders, for example).

I don't suppose theres some hybred mode possible? The newest rendering engine while still serving the ie10 code?
Probably break everything else though I guess.

On Saturday, October 4, 2014 6:43:15 PM UTC+2, 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