We're having this internal debate where some people think that the user shouldn't use the browser's "back" button when filling a multi-page form (for security reasons), and that the whoever hits the "back" button should be forced to start over.

I'm not really sure about this. I mean I understand the security concerns, but I also usually hate to take over the default behavior of browser controls. It's still a valid point of view though.

What do you think? should the user be able to go back to previous form pages using the browser's back button? and why?

  • 7
    What are their security concerns? Feb 14, 2011 at 14:11

4 Answers 4


You shouldn't override the default behaviour of the browser.

You should really be able to cope with the user hitting "back" and returning to the previous state, however, I have seen something along the lines of the following added to the page:

Please don't use the browsers back button to navigate between pages

and if you do click the back button it aborts the whole process.

If you really can't cope with the use of the browser's back button you must provide a "back" button within your process for people to use.

  • 1
    You'd think if it it was the no.1 sin in 1999, it's taboo now. :)
    – srcspider
    Feb 18, 2011 at 8:48
  • 4
    Whenever I see something like that it makes me angry. Why should I have to override my muscle memory to use your custom back functionality? Why couldn't you just get it right like 99% of the sites I visit so I don't have to think about it? And I'd love to see a study on how many people disregard, fail to notice, or forget about notices like that and use the back button anyway.
    – Pam G
    Jun 6, 2011 at 21:40
  • @PamG Exactly! I can’t believe this is the accepted and most up-voted answer, although I agree with the first paragraph of course.
    – Crissov
    Feb 5, 2016 at 20:29

Yes, the user should be able to go back using the browser's back button. Wherever possible consistency should be maintained, as should meeting user expectations. For many users 'going back' on a web browser whether via the button or a shortcut (including dedicated shortcut buttons in mice etc) will be automatic behaviour which will be difficult for user to overcome, or indeed remember to try and overcome.

If you really really have to disable standard functionality then step 1 should be to rethink and work out if you really really really need to disable it! :-)

Returning the user to the start could result in a lot of lost work and effort, depending on how many steps there in the process, where the user may have only been expecting in a worst case to lose the effort invested in the current page. If the back functionality is going to be modified to take a user to the start of a process there should be warning/confirmation.


Even though this is an older post, the core issue remains.

ChrisF makes a valid point--core functionality of the Web browser shouldn't be disabled unless absolutely necessary. Also, adding text instructions may often be overlooked/ignored by users.

A good possible solution is to incorporate some JavaScript that will alert the user if they attempt to use the back button.

  • Even better: 1) Phrase the text clearly and unambiguously, and tell users what they need to know when they need to know it, so that they never need to go back. 2) Wherever possible, put all the form's controls onto the same page, so the user needn't click back but can just scroll up.
    – Rosie F
    Jun 4, 2017 at 10:58

Users often get confused when provided with a multi - step form. And if you generally see a users behaviour when he feels confused is to hit the back button and restart it all again. So they will anyhow demand it. However as ChrisF mentioned you should provide users a warning message as to pressing back will take you out of this multi- step form.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.