On Wed, Jun 23, 2010 at 6:50 AM, Thomas Broyer <t.bro...@gmail.com> wrote:
> > > On 23 juin, 03:52, Pascal <zig...@gmail.com> wrote: > > Hi, > > Has the workaround been included in the codebase somewhere? Is there a > > chance that there will be a point release soon? > > There's been a change at the compiler-level instead: > http://code.google.com/p/google-web-toolkit/source/detail?r=8300 > > I don't think we'll see a 2.0.4 though, I guess the plan is to just > ship it with 2.1 when it'll be ready. > (remember last year when IE8 finally went out? –there was a workaround > though– or Safari 4 and its "expression too deep" errors? or Firefox > 3.5 and its regression re. mouse events on scrollbars?) > See http://code.google.com/p/google-web-toolkit/issues/detail?id=3455, > http://code.google.com/p/google-web-toolkit/source/detail?r=5641 > This was all fixed in the next release, but it took some time between > the report, the fix, and then the release. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.