Thanks for the explanation.
I find this very interesting. This means I'll be able to extend
the CrossSiteIframeLinker Linker and overwrite
the fillSelectionScriptTemplate() function to include all required scripts
with sth like document.write()
or document.getElementsByTagName("head")[0].appendChild()
And to guarantee that they are present during onModuleLoad() there should
be a couple of workarounds, like checking in every entry point module if
scripts are ready (with sth like typeof LibraryName === "undefined") and if
not postpone startup until they are ready.
Or maybe taking a closer look at the regular IFrameLinker. From what I see
right now it basically uses document.write("<script
defer="defer">module.onInjectionDone('module')</script>") and then
calls maybeStartModule() which hopefully will have code I can reuse.
And the reason google didn't include this in their CrossSiteIframeLinker is
because they didn't want to use document.write() for this linker?
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/3ExS87Gc7XcJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
