Hmm. It's a fair point. On the other hand, you don't *have* to upgrade right away. Assuming third-party libraries want to upgrade, it might be easier to make "works with 2.6" mean "works with a separate ie10 permutation" rather than having to support two modes for 2.6.
This doesn't scale, but if there's a specific third-party binding you're concerned about, perhaps it's possible to write your own rebind rule to bind it for ie10? - Brian On Wed, Oct 23, 2013 at 2:08 AM, Jens <jens.nehlme...@gmail.com> wrote: > 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 by default and you can enable it > once you know your app and all your 3rd party libraries are ready. > > -- J. > -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
