On Saturday, May 25, 2013 12:57:09 AM UTC+2, Brian Slesinsky wrote: > > Following up on discussion in: > https://gwt-review.googlesource.com/#/c/2900/ > > There's been some talk about dropping IE 6/7 and it's confused the > conversation a bit. I'd like to distinguish between what happens short term > and how things will look by our next stable release. I expect that by GWT > 2.6, IE6 and 7 support will be gone. People who use stable releases have > opted in for big-bang, everything changing all at once and they can do it > on whatever schedule is convenient to them, including not upgrading until > they're ready. > > Short-term for those of us at trunk, it's a whole lot easier if we take it > one step at a time. First add the new stuff, perhaps hiding it behind a > flag. Turn it on by default. Then remove the old stuff. If these land as > separate commits then we can verify that each one didn't break our > customers before moving on to the next. I realize it's more work than a > single atomic change, but it's a lot smoother. > > I'm fine with waiting on some patches until IE6/7 goes away entirely, but > it's also possible to move a few steps forward on some things without > waiting on a different patch. > > At the moment, I don't know anyone specifically working on removing IE6/7, > which should proceed in a similar way. We've agreed that it should be done, > but someone has to do it, and I'd expect it also to go one step at a time. > I think the first step is to make sure everyone knows how to enable or > disable the IE6/7 permutation (are any code changes necessary?), and the > next step is to change the default so it's off. >
Does Google still support IE6/7 on some apps? I thought you only supported IE9+ If you don't support IE6/7, and we choose to drop IE6/7 support in the next release, then 'master' could have a transition period where RPC simply wouldn't work in IE6/7 without removing the ie6 permutation. BTW, disabling the IE6/7 permutation is only a matter of <set-property name="user.agent" value="ie8,ie9,gecko1_8,safari,opera"/> right? Removing support would start by removing the ie6 permutation and then cleaning up the code by removing now-unused code, and finally possibly clean up further by refactoring some code that was used in both ie6 and ie8 to better take advantage that it'd now only be running in IE8. I otherwise agree about the principle: first deprecate, add a flag, then turn the flag off by default and remove the code then remove the flag (or remove everything in one go). Well, anyway, that's the basis of trunk-based development which is what we chose to use for GWT. -- 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.
