Issue

When running a web application, the history page stack is changed when the user refreshes the page.

For instance, if the user navigates through three pages in the application and in the last page (Page 3), they push a button with the event Close page that is configured to set All to close the pages. This will result in the application going to the first page (Page 1). But, when the user refreshes the browser when navigating, the application navigates back to Page 2 instead.

Environment

Web application

Cause

This is the standard application runtime behavior when the refresh button in the browser is clicked.

The history page stack is reset and the page where the user clicked on refresh, becomes the first page in the stack. 

So, in our example, if the user clicks on the refresh button when viewing Page 2, when on Page 3 they click to close all the pages, the application will take the user to Page 2, and not Page 1.

Solution/Workaround

The application developer will have to design the app to navigate to the desired pages considering the end user may click on the browser refresh button.