Contents
Alas, during testing, the vast majority of user-initiated overlays at the tested sites did not close as the users clicked the browser “Back” button, but instead sent them way back past the overlaid page. This user expectation of “click ‘Back’, exit overlay” was observed during testing on both desktop and mobile sites, for all types of overlays.
There are so many ways to stop the browser back button most popular and will work in all conditions. You can add code to the first or previous page to force the browser to go forwards again and again so when the user tries to back to the previous page the browser will take him again in the same.
Why do we use the back button in web navigation?
Indeed, the “Back” button has long been a staple of web navigation, and users’ often decades-long experience with using it has caused them to develop a very specific mental model of how it should behave.
Where does the back button take the user?
And therein lies the rub: the browser “Back” button takes the user back to their previously visited URL, which isn’t necessarily the same as what the user perceived to be their previously visited page.
When you click on the back button, the values in hidden fields retain the same value as when you originally left the page. So the first time you load the page, the input’s value would be “no”. When you return to the page, it’ll be “yes” and your JavaScript code will trigger a refresh.
(i.e check whether the user has logged in from login page and user has proper keys or not) if he doesn’t that he should be redirected to the login page. You could do this by applying proper authentication on your application. Not a solution. The problem is not caused by clicking a link on an active page, the problem is the cached pages.
Hope that helps.. You should use a hidden input as a refresh indicator, with a value of “no”: When you click on the back button, the values in hidden fields retain the same value as when you originally left the page. So the first time you load the page, the input’s value would be “no”.
What happens if you disable the back button?
If you are trying to stop them, at the client side, from viewing a page you can’t. If javascript is disabled then you scripting efforts are a waste. If they manually look up their history and go to the page, or have bookmarked a page and then go to the bookmark, then you’re back to square 1.
Clicking the Back button now takes the location back to #2, demonstrating that page states have successfully been added to the history. But note that clicking the Back button doesn’t automatically return the page to its previous state.
Should a web-based UI rely on the browser back button?
A web application should always strive to be compatible with the browser’s back button. That is, using the back button should have deterministic results within that application that match expected behavior (global consistency).
Drag and drop is a great way for users to interact with your web applications. But the usability gains will be lost if, after spending time moving through your application, users click the Back button expecting to go back a page and instead go back to their Start screen. In this article “Hello!