On Wed, Oct 23, 2013 at 11:59 AM, Jens <[email protected]> wrote:
> Hmm. It's a fair point. On the other hand, you don't *have* to upgrade >> right away. >> > > Hehe sure, but its hard to resist Java7, @GwtIncompatible support and > compiler/code splitting bug fixes ;-) > > But maybe I misunderstood Matthew's post? I was under the impression that > with either solution 1 or 2 I could upgrade right away to 2.6 without > problems. In order to stay on the safe side when upgrading to 2.6 the only > thing I need to care about is to make sure that IE10 permutation is > disabled (which means I put myself in the same situation as with GWT 2.5.1 > which does not know IE 10). > You can certainly try it and most things will likely work, for now. The only issue is if you're using some third-party library that expects the IE10 permutation to be there, and might behave strangely with IE10 if the IE9 permutation gets used instead. We have to decide which configuration people writing third-party libraries should test their code with for 2.6; they aren't likely to test everything and will probably just test with 2.6 and the defaults. It seems better in the long term if they assume the IE10 permutation is there. - Brian -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
