See above comment on redirection navigation cases.

This feature makes use of the "safe" aspect of window scope (propagation only, not disposal). So, if we have a variant of windowScope without the onBeforeUnload POST, this should continue to function.

Introduced "org.icefaces.replayNavigationOnReload" context parameter to allow the disabling of the non-standard (but useful) behaviour. The parameter's value defaults to "true".

Turning off navigation replay by default.

Changing ReloadAfterNavigationFix navigation handler to bring navigation behaviour closer to the standard JSF behaviour proved impossible to achieve.
When non-redirect navigation and redirect navigation rules are mixed it's not possible to determine with certainty if a request is just for page reload or a request for loading a different page.

For example when page A is loaded and a non-redirect navigation is made to page B all the forms in the rendered page have now page B's url. If we reload page A ReloadAfterNavigationFix navigation handler will make sure the navigation is replayed and B's content is shown again. If we click on a command link with AJAX disabled the requested page is B because the forms use B's url now, so it's impossibile to determine now that what the user really wanted was page A content rendered.

The compromising solution was to make the replay navigation feature configurable. There are applications or environments (like portals) that use only non-redirect navigation rules. These application become much more natural to use once replay navigation feature is introduced.