The problem was actually caused by a window.onload conflict from another js script... Chrome v19.0.1084.46m debug is working just fine. (tail between legs)
On Tuesday, May 15, 2012 3:04:40 PM UTC-4, Rori Stumpf wrote: > > > Carlos, I have Chrome 18.0.1025.168 m - it just spins it's wheels & > nothing happens. I see there is a newer update. > KevMo, thanks for the download. > Clint, this is for Windows 7 64-bit, but thanks anyway. > > You know, sometimes it would be good if stuff just worked. I've been using > GWT for a while now, and debugging is a consistent irritation! > > > On Tuesday, May 15, 2012 2:49:54 PM UTC-4, Carlos Silva wrote: >> >> On Tue, May 15, 2012 at 6:32 PM, Rori Stumpf wrote: >> >>> I made the mistake of upgrading to FireFox 12. I thought Chrome would >>> work for GWT debug, but that pig still isn't flying. >>> So... where can I download FF 10? I've spent 1/2 hour trying to find it >>> on the web, everything I found points back to FF12. >>> >> >> How come chrome doesn't work? I'm using the latest beta (19.X) and it >> works. >> > -- 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/-/3yqod1xDdJ0J. To post to this group, send email to google-web-toolkit@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.
