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