This looks like the logical conclusion to my question. https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Isolated-Imports-Proposal.md
Since the aboveis probably several years down the road I wonder if anyone has any more ideas or workarounds in how to work with GWT/jsinterop and foreign js libraries __loaded in GWT context__ (iframe) in the immediate future... Anyone? Thanks in advance. On Thu, May 26, 2016 at 1:01 PM, Vassilis Virvilis <[email protected]> wrote: > Hi, > > This issue has been discussed before > https://github.com/gwtproject/gwt/issues/9264 > > Here is the problem in my own words: > > When a script is injected GWT has the option to inject it in the > TOP_WINDOW ($wnd) or in the iframe window where GWT code is located > normally. > > Case 1: Insert in $wnd > > Everything works but the page is polluted with the scripts you inject. > This is not a problem when the GWT application controls the whole page. It > is however a problem when GWT program is loaded as part of a page (Widget). > Then all kind of problems may arise due to javascript libraries clashing. > > Case 2: insert in iframe window (default) > > The script is loaded but jsinterop assumes that the scripts are loaded in > $wnd which is not true. > > Question: > > Is it possible to > 1) add a compile time flag in jsinterop that will not prepend $wnd in all > global objects defined by the script ...OR... > 2) add a namespace JsPackage.LOCAL (as opposed to JsPackage.GLOBAL) option > that does not imply $wnd ...OR... > 3) do something that fixes the problem somehow! > > -- > Vassilis Virvilis > -- Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
