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.
All apps should support the back button. Everyone uses it and you cannot tell your users to change their browsing habits just for your webpage. Yes it's petty, but so are users. Like me, for example. No joke, I will not use a web page/app that does not support the back button. It just frustrates me the first time it happens and I look for the next Google result.
发布评论
评论（5）
我个人的观点是，任何不能合理优雅地处理后退按钮（如果不完全正确）的网站都会在可用性方面遭受巨大打击。 人们了解后退按钮。 更重要的是，他们喜欢它。
页面加载速度可能很慢。 我不想每次打开列表上的项目只是为了返回该列表时都必须完全加载页面。
使用 POST+REDIRECT+GET 和其他习惯用法，您可以通过后退按钮获得良好的行为，这就是您应该努力的目标。
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.
我认为所有网络应用程序都应该支持后退按钮。 如果它破坏了您的应用程序并且您无法为其编写代码，那么至少在导航离开事件上放置一些 JavaScript，让用户知道不支持后退按钮，并且使用它可能会导致工作损失。
当您单击后退按钮并进入非工作页面并且最终丢失了正在处理的内容时，这是令人沮丧的。
支持它或者至少确保用户知道他们不能使用它，并在他们出于习惯点击它时提醒他们。
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.
是的，是的，他们应该这样做。
Yes, yes they should.
您绝对应该支持网络应用程序中的后退按钮。
用户确实认为该功能受到支持。
您可以在此博客文章 http://blog 上了解 PRG。 andreloker.de/post/2008/06/Post-Redirect-Get.aspx 或维基百科 http://en.wikipedia.org/wiki/Post/Redirect/Get
You should definitly support the back button in a web app.
Users do really assume that this features is supported.
You can read about PRG on this blogpost http://blog.andreloker.de/post/2008/06/Post-Redirect-Get.aspx or on wikipedia http://en.wikipedia.org/wiki/Post/Redirect/Get
所有应用程序都应该支持后退按钮。 每个人都使用它，你不能告诉你的用户仅仅为了你的网页而改变他们的浏览习惯。 是的，这很琐碎，但用户也是如此。 比如像我这样。 不是开玩笑，我不会使用不支持后退按钮的网页/应用程序。 第一次发生的时候我很沮丧，我寻找下一个谷歌结果。
All apps should support the back button. Everyone uses it and you cannot tell your users to change their browsing habits just for your webpage. Yes it's petty, but so are users. Like me, for example. No joke, I will not use a web page/app that does not support the back button. It just frustrates me the first time it happens and I look for the next Google result.