State-discard-callback behaves incorrectly with browser navigation

[sportlog]

Hi,

the statediscard callback works fine when changing the routedApp or the metarouter. ("registerAllowStateDiscardCallbackAsync")

However it behaves incorrectly with browser navigation.
Problems:

• When navigation back from a "dirty" route the stateDiscard-Callback is not called
• When navigation forward again the stateDiscard-Callback is called, while seeing the not dirty route

This limitation is due to the "hashChange" event, which does not allow event interception. (compared to onbeforeunload).