So it appears that this is caused by JSNI methods somehow being morphed when the GWT app is compiled. I don't know how, but I do know that calls to Chrome proprietary APIs aren't working correctly. I modified my code to do the following:
Java method calls JSNI method JSNI method calls raw JavaScript method in base app loading page (a JSP page) ... and it now works. So the GWT compiler is doing something funny to JSNI methods that cause the Chrome API calls not to work as expected. Anyone know what's happened there? - Tim -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
