I did a system test on a new ASP.NET app. I encountered several exceptions when using the BACK button in my browser (IE 7).
I stated in a review-record that the web-app must support the use of a BACK button (or at least handle it gracefully with for example session-time out warnings). The teamlead did not agree with me as he stated that a web-app should not support working with the back-button by default.
Do you agree?
My personal opinion is that any website that doesn't handle the back button reasonably gracefully if not entirely correctly is taking a huge hit in usability terms. People understand the back button. Moreso, they like it.
Pages can be slow to load. I don't want to have to fully load a page each time I open an item on a list just to go back to that list.
With POST+REDIRECT+GET and other idioms you can get nice behaviour with the back button and that's what you should strive for.
I think that all web apps should support the back button. If it breaks your app and you can't code for it, then at least put some javascript on the navigate away event to let the user know that the back button isn't supported and using it might cause loss of work.
It's frustrating when you click a back button and get to a non working page and you end up losing something you were working on.
Support it or at least make sure a user knows that they can't use it, and remind them when they click it out of habit.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With