Re: [gwt-contrib] Re: Upgraded from GWT 2.6 to 2.8 - now Chrome Extension API doesn't work...

If it is the linker, going back to your 2.6 code and changing to the current xsiframe linker might show the bug - if so, you know it is related to the default linker change. If not, debugging your JSNI to see what the value of chrome is before and after the GWT version change will be helpful,

Re: [gwt-contrib] Re: Upgraded from GWT 2.6 to 2.8 - now Chrome Extension API doesn't work...

On Wednesday, May 3, 2017 at 1:08:14 PM UTC-7, Goktug Gokdogan wrote: > > Maybe related to $wnd, but here we are basically shooting in the dark. You > should debug your code and tell us where it behaves unexpectedly otherwise > we cannot help much... > I have indeed debugged the code, and

Re: [gwt-contrib] Re: Upgraded from GWT 2.6 to 2.8 - now Chrome Extension API doesn't work...

Maybe related to $wnd, but here we are basically shooting in the dark. You should debug your code and tell us where it behaves unexpectedly otherwise we cannot help much... On Wed, May 3, 2017 at 12:57 PM, TimOnGmail wrote: > Ok... here's the client app side - I haven't

[gwt-contrib] Re: Upgraded from GWT 2.6 to 2.8 - now Chrome Extension API doesn't work...

Ok... here's the client app side - I haven't tried running this as-is, since it was culled from a much bigger piece of code. But this is the gist of it: package com.example; public class ChromeAPIExample { private static final String CHROME_APP_ID = "..."; // Replace with actual Chrome

[gwt-contrib] Re: Upgraded from GWT 2.6 to 2.8 - now Chrome Extension API doesn't work...

This might be related to linker changes but not sure that in which version that was changed. Pls provide the code snippet that was working before and no longer working. On Tuesday, May 2, 2017 at 6:00:50 PM UTC-7, TimOnGmail wrote: > > No no, I had been calling Java -> JSNI -> Chrome ; that

[gwt-contrib] Re: Upgraded from GWT 2.6 to 2.8 - now Chrome Extension API doesn't work...

No no, I had been calling Java -> JSNI -> Chrome ; that worked in GWT 2.6 Now, in GWT 2.8, the above does NOT work. I modified the code to do: Java -> JSNI -> JavaScript that's not wrapped in a JSNI method (it's in the app's main JSP file) -> Chrome, and it works again. So, JSNI methods

[gwt-contrib] Re: Upgraded from GWT 2.6 to 2.8 - now Chrome Extension API doesn't work...

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

[gwt-contrib] Re: Upgraded from GWT 2.6 to 2.8 - now Chrome Extension API doesn't work...

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