Some of us are stuck on GWT 2.4 since the 2.5 release notes make a point of saying that they no longer support Chrome Frame for IE. Since we support hospitals and large mining corporations that still run IE6, if they don't use Chrome Frame, it's practically unusable. (Yes, I know there's half a dozen forum posts saying "oh actually 2.5 still supports it", but as long as the release notes say it "officially", management won't allow us to upgrade.)
I think the bigger point people here are making is that *Google* Chrome made a radically change that made the *Google* Web Toolkit to break. No backwards compatibility whatsoever. Even when Microsoft's Internet Explorer browser changed their rendering engines, etc, they still included the 'Compatibility Mode' so that older webpages could be rendered correctly. On Monday, January 14, 2013 9:26:19 AM UTC-7, Thomas Broyer wrote: > > > You mean "while they wait for you to update", right? > > I don't get why people get angry here: there was a bug in GWT, it was > fixed 8 months ago in trunk and was released nearly 3 months ago (before > users on the stable channel of Chrome could even notice). There's an easy > workaround too for people not ready to update to GWT 2.5. > So what's the problem actually? You didn't test your apps with beta or dev > versions of your browsers (that gives you 6 to 12 weeks to fix issues > before your users can notice), you're 3 months late on updating to the > latest stable release of GWT *and* you cannot deploy an updated version > (recompiled with the workaround) quickly. You can blame GWT for using a > "beta", though rather stable, API (requestAnimationFrame) to smooth the > rendering of your app and having made assumptions on the value it received > as argument and the exact time it'll be called back, but GWT is not the > only one to blame by an order of magnitude. > Perhaps you have the resources to fully regression test all of your applications every week on all 8 or 9 different supported browsers, plus dev/beta versions, but in the real world of enterprise software, that's simply not feasible. Stable software should remain stable. If a customer upgrades his version of Windows, I shouldn't expect the new version to suddenly start working strangely because of a radical change in how animations are rendered. A similar concept should apply for web browsers. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/O7y-MTGqdRoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
