On Wednesday, August 18, 2010 16:33:04 Ray Cromwell wrote: > I have a feeling this is actually working as its supposed to on Chrome, but > silently failing on the other browsers. The stack trace indicates that a > JSON payload that it thought was a JSO object turned out to be a JS Number, > so the JSNI callback failed. Why this would work on other browsers beats > me, but I'll track it down in a few hours.
Thing is.. on other browsers, we still get a proper response from the RPC request. I'm currently noticing that r8563 is fixing some of our responses from the server. Before this patch, I didn't get any RPC response that would actually produce something else than an exception on Chrome. However, this is now getting better. I'm trying to see what's the pattern here. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
