Sounds great, but is there a reason that we're now starting at IE9+ and not IE10+, thus giving us typed arrays, web workers, web sockets, etc? I only ask because the kind of case where you are giving up User (and Widget, RPC, Timer, and other fairly high-level apis) seems to suggest that you might not be writing for a browser at all (htmlunit, nashorn, web worker, node.js).
Dan definitely has a point that if we're supporting modern browsers for a core chunk of functionality, we really shouldn't let 'modern' be 'whatever junk still happens to be running rather tha updating'. And besides, I can't always be That Guy pushing to keep all versions forever, just because IE8 is still 11% of North America's browser usage (really: http://theie8countdown.com/). If we're cutting a browser for being old/bad/whatever in Core, but leaving support for it still in User, we should consider carefully why we *aren't* cutting deeper. On Monday, June 30, 2014 2:59:12 PM UTC-5, Goktug Gokdogan wrote: > > We are planning to drop support for IE8 if the application doesn't inherit > c.g.gwt.useragent.UserAgent and hence not have browser permutations. > > Nearly all of today's apps inherit User so they will not be affected by > this change. In the future more apps will only inherit Core however they > shouldn't need to pay price of IE8 support (currently they do because there > are no permutations in Core). > > Let me know if you have any concerns. > > - Goktug > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/45b68163-0d07-4a6c-9932-412232e2f71d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
