On Monday, January 14, 2013 2:53:52 PM UTC+1, John V Denley wrote: > > Yup, same problem for me at www.DiaryBooker.com/demo - click any > appointment location to create a new appointment and you see it right > there! > > This has actually happened before and a few updates later it had gone away > again! > > I'm not sure what version of GWT is currently live, but my current > development version is not showing this issue, trouble is I am halfway > through a massive update, so cant make any changes to the current live > version >
You mean that cannot even create a branch in your SCM from the commit you last deployed, apply the workaround and re-deploy? And you didn't plan for that eventuality? > and Im getting complaints from my customers.... I have had to tell them to > use Internet Explorer while we wait for Google to fix it!! > 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. The Web is a moving target: browsers update and can break your code as soon as you (or the lib you use) a) make assumptions on browsers behaviors, b) use "beta" APIs or c) use hacks or workarounds. When working with web technologies (whether it's GWT, jQuery or vanilla JS), it's very important to regularly a) test in beta or dev versions of your browsers, b) update to the latest release of the libs you use and c) be prepared to re-deploy quickly. -- 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/-/4BmvA88HyfAJ. 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.
