It looks like the purpose of registering the unload handler for any Window
event is to avoid IE6-10 era memory leaks. From the notes on the MDN page,
removing those other handlers will break the page when the bfcache is in
use, but our use of the unload handler will opt GWT pages out.
The
Yes: https://developer.mozilla.org/en-US/docs/Web/API/Window/unload_event
Apparently, this happens when you use Window.addXxxHandler (and for
instance the default PlaceController's delegate calls
Window.addClosingHandler, which registers an unload handler but is only
interested in the
Hello.
Browsers running our GWT application (version 2.11) have recently (this
week) started reporting errors like this one:
[{"age":41550,"body":{"columnNumber":192,"id":"UnloadHandler
","lineNumber":3210,"message":"Unload event listeners are deprecated and
will be
