Closed GoogleCodeExporter closed 8 years ago
This issue is reproducable, but doesn't seem to have negative effects (when
navigating back everything is still working normally). This problem was already
reported with Issue32, so this issue will now be merged together with Issue32.
Original comment by sven.strohschein@googlemail.com
on 3 Oct 2011 at 10:49
Fixed via Issue32:
Status code 0 is sent by some browsers when the browser/user navigates to
another site/application and is actually not an error, but GWT inteprets this
as a StatusCodeException. In the case of GWT applications it should be an
unimportant status code because the GWT module is unloaded in that case.
Status code 0 is now handled correctly by GWTEventService and will no longer be
logged as an error (fixed in the trunk version and in the upcoming 1.2 release
candidate).
Original comment by sven.strohschein@googlemail.com
on 3 Oct 2011 at 4:04
Original issue reported on code.google.com by
ker...@gmail.com
on 2 Jun 2011 at 9:02