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

2017-05-02 Thread TimOnGmail
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 calling Chrome APIs directly appear to no longer be 
working.

Does that explain it better?

- Tim


On Monday, May 1, 2017 at 4:11:29 PM UTC-7, Colin Alworth wrote:
>
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/aaeae823-f328-48ad-936a-9175a4c54cf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2017-05-02 Thread 'Goktug Gokdogan' via GWT Contributors
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 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 calling Chrome APIs directly appear to no longer be 
> working.
>
> Does that explain it better?
>
> - Tim
>
>
> On Monday, May 1, 2017 at 4:11:29 PM UTC-7, Colin Alworth wrote:
>>
>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/6a60f23f-0cc4-48fe-bdfa-edd5f49fae1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.