What had been the care previously? Were you calling the chrome methods in some way other than through JSNI? Java methods can't call raw JavaScript without JSNI (or JsInterop, which didn't exist in GWT 2.6). Otherwise I'm not sure what you changed it _from_ to get to the psuedocode in your post.
I'm not aware of breaking changes that should have happened (though it has been three years between the releases). It is possible that you were using JSNI in a way that probably shouldn't have worked previously, and since then it has been "fixed"? On Monday, May 1, 2017 at 5:02:09 PM UTC-5, TimOnGmail wrote: > > 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 Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/a47e43d7-22da-4bc5-8f47-0462ef235888%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
