We were also getting this issue when we migrated it to 2.8.2. With the
upgrade, we had to define a custom linker name instead of overloading the
"xsiframe" name like we were doing in 2.7. We thought that was enough but
then this error occurred. The fix was to basically replicate this deferred
binding that GWT had defined in CrossSiteIframeLinker.gwt.xml, but for our
custom linker name.
<replace-with class="com.google.gwt.core.client.impl.ScriptTagLoadingStrategy">
<when-type-is
class="com.google.gwt.core.client.impl.AsyncFragmentLoader.LoadingStrategy"
/>
<any>
<when-linker-added name="custom_linker" />
</any>
</replace-with>
On Wednesday, May 25, 2016 at 10:57:24 AM UTC-7, clou...@gmail.com wrote:
>
> I did add a custom linker in order to get HTTPS sort of working for SDM
> debugging. A very simple class derived from CrossSiteIframeLinker and only
> overriding getJsDevModeRedirectHookPermitted(...). No custom linker was
> used previously.
>
> Feels like a regression to me... I guess I'd need to check what linker was
> used in GWT 2.5 and which is used during SDM, as the issue didn't manifest
> in either place (only in production).
>
--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
