On Wed, Oct 23, 2013 at 11:59 AM, Jens jens.nehlme...@gmail.com 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
I would tend to vote for option 2.
With option 1 nearly everyone will need to disable the ie10 permutation
anyways because not only own code must be updated but also 3rd party
libraries must provide updated rebind rules which may take some time. So I
think it feels better if ie10 is disabled
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
[Moving discussion to gwt-contrib]
If we don't fallback, we'll need to figure out how to handle the GWT 2.6
release. Possible options:
1. Enable ie10 permutation without fallback. When users upgrade, they
need to simultaneously fix their code by adding appropriate rebind rules
for ie10. Or
