IE11

[jgindin]

I'm hoping someone can comment on getting full-fledged support for IE11 into GWT 2.6. I seem to remember that Vaadin was taking the lead on this, but the link I had to a Google Doc with the GWT Road Map is now a protected link.

IE 11 support is a **huge** deal for us, and it's due to be out in GA in just over a month...

Thanks in advance for the updates,

Jay

[Thomas Broyer]

Bad news: IE10 still has no proper support in "trunk" (I think Vaadin will finish it before 2.6 though), even less so IE11… (I wouldn't count on it for 2.6; but if you really need it, please take the plunge and contribute patches: http://www.gwtproject.org/makinggwtbetter.html)

Good news: IE10 and IE11 will both happily load your GWT app using the ie9 permutation if you switch them to the IE9 document mode (using X-UA-Compatible)

[David]

Thomas,

 

What are the known issues ? We have been running our apps for quite some time on IE10 (build with 2.4.0 and 2.5.1) with nothing really blocking.

Does it hurt that we target IE=edge ? Should we really set IE9 as document version ?

 

David

--
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-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

[Thomas Broyer]

On Monday, September 9, 2013 11:16:27 AM UTC+2, stuckagain wrote:

Thomas,

 

What are the known issues ? We have been running our apps for quite some time on IE10 (build with 2.4.0 and 2.5.1) with nothing really blocking.

Does it hurt that we target IE=edge ? Should we really set IE9 as document version ?

According to https://code.google.com/p/google-web-toolkit/issues/detail?id=8063, IE10 should work OK with the ie9 permutation in its "IE10 Standards" mode. I think "proper support" here mostly means "new features" (such as TypedArrays and pointer events).

I have no idea what would be needed for IE11 though (but see https://code.google.com/p/google-web-toolkit/issues/list?can=2&q=ie11)

[jgindin]

The issues noted by Thomas are exactly those which are causing us problems right now, and will impact some of our significant customers / partners.

I'm digging into what exact issues come up once we're able to force the GWT bootstrap process to download the IE9 permutation (instead of the FF permutation, which truly does not work).

Can someone from Vaadin chime in as to the state of the IE 10/11 support will be in GWT 2.6?

Thanks,

Jay