Hello all... I'm a developer on a project that uses GWT. We had been using GWT 2.6 for a long time, and finally moved to GWT 2.8 w/Java 1.8.
Part of this project is a Chrome extension, where our web app needs to communicate with the extension. This was working fine until we upgraded out project. Now, there may be other code-related things going on that is causing this, but I thought I'd check here to see if anyone knows of GWT 2.8 possibly breaking Chrome extension APIs, specifically the Chrome "Message Passing" API: https://developer.chrome.com/extensions/messaging The web app attempts to connect to the extension using chrome.runtime.connect(appId). This worked fine in the past, but has now stopped working (in prior versions of our code, the extension receives the connection attempt; in current code, the connect method returns a valid "port" object, but the extension never receives the connection). Anyone know of any conflicts between GWT 2.8/JsInterop/etc. and Chrome's proprietary APIs? - 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/a6ed7e1f-bf7c-4418-a6a1-2d2a733d8594%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
