Thanks Thomas, <add-linker name="std" /> fixes the issue.
It does seem like it might be a browser bug. It shouldn't be possible to ever bypass the cache I don't think. I tried to build a small gwt program to reproduce the error but my small program worked perfectly. Still recurs everytime in the app where I found the problem though. On Mon, Oct 20, 2014 at 10:49 PM, Thomas Broyer <[email protected]> wrote: > IIRC, Brian changed the behavior of the xsiframe linker to match the > direct-install linker, because most browsers would otherwise not display > the source maps. There should be flag to turn it off and go back to the > previous behavior. > It however looks like a browser bug worth reporting. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/b46f94bc-4dc3-45f1-822f-d2df59f7cc8a%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVjDYe9X1s5wjXgqVPGcusHEW-4gZZ-aooCQW9T3tnWESQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
