Fragment handling and asynchronous ui update conflict

Hi,
we have an application where we use fragments to navigate between different views which update asynchronously.
When clicking the browsers back button while an asynchronous update is still pending sometimes the forward browser history gets lost. We suspect that the location is updated by every single rpc response and not only when we set the fragment explicitly. You can see that behavior using the network monitor in chrome or network tab in firebug.

Attached please find a small Vaadin application where we reproduce that issue.

Is there any best practice or workaround to solve this issue?

best regards and many thanks,
Marku
14103.zip (16.8 KB)