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, or whatever the different wiring is (chrome.runtime.connect perhaps).
My guess (which is what Goktug is pointing to I think) is that you really should have all usages of chrome prefixed with "$wnd." so that there is no ambiguity about which object is being used, and which frame it is from. If the above code is simple enough to demonstrate the issue, can you put a minimal project together so that we can reproduce the issue, including build instructions? Aside from that and the above suggestions (which is just rehashing of http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsJSNI.html and the earlier emails), we don't really have anything to go on... On Wednesday, May 3, 2017 at 3:22:27 PM UTC-5, TimOnGmail wrote: > > 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 wasn't able to figure out what was > going on, which is why I posted this here. :-) > > What level of debugging are you hoping for? The Chrome JavaScript APIs > are a bit obtuse to debug. > > The above example is pretty simple - I can send you a working example if > you like, a complete Eclipse project plus an example Chrome app to > demonstrate the issue. > > - 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/cc64048c-d87b-43c4-b96d-39b147729dd6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
