blocks|key|4258414|text|我想我可以把这些回应归纳为|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4258415|除非你无法避免，否则你永远不应该这样做。即使那样你也不应该。|blockquote|4258416|听起来差不多对。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|I|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|J|8|@]|9|@]|A|$]]]|G|$]]

I think I can sum up the responses as 

<blockquote>
 You should never do that unless you absolutely can't avoid it. Even then you shouldn't.
</blockquote>

Sounds about right.

blocks|key|5444986|text|只有在预期的情况下才打破“后退”按钮(如果在您的网站上的某个事件之后不返回是有意义的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5444987|Mozilla做了一项关于人们如何使用浏览器的研究，“后退”按钮的结果令人印象深刻：|5444988|后退按钮比任何其他导航元素使用的频率都要高得多(我们指的是后退、前进、再发、停止和主页按钮)。93.1%25的研究参与者至少使用一次后退按钮，平均每个用户在5天内点击66.2次--这比Reload按钮多点击3倍，比Home按钮多10倍，比前进和停止按钮多30倍！来源|blockquote|offset|length|5444989|我经常使用后退按钮，当我不能使用它时，我讨厌它。|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.mozilla.com/metrics/2010/07/01/firefox-main-window-study-a-heatmap-visualization/^0|0|0|3L|2|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|T|8|@]|9|@$G|U|H|V|1|W]]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Only break the back button if it is expected (if it makes sense to not go back after an event in your website).
Mozilla did a study about how people are using its browser and the results for the back button are impressive:
<blockquote>
The Back button is used far more often than any other navigation element (by which we mean the Back, Forward, Reload, Stop, and Home buttons). 93.1% of study participants used the Back button at least once, and on average, each user clicked Back 66.2 times over the 5 days – that’s 3x more clicks than the Reload button, 10x more than the Home button, and over 30x more than the Forward and Stop buttons!
<a href="http://blog.mozilla.com/metrics/2010/07/01/firefox-main-window-study-a-heatmap-visualization/" rel="noreferrer">source</a>
</blockquote>
I use the back button a lot and I hate it when I can't use it.

blocks|key|5444934|text|打破后按钮就像踩坏了汽车的刹车踏板。用户期望它总是起作用，当它突然不起作用时，混乱就会发生。back按钮可能是浏览器中使用最多的UI功能，因此它可以以任何方式改变它的行为，充其量是没有好处的，在最坏的情况下，会导致用户混淆和放弃(或增加客户支持成本)。即使它让用户回到原来的位置，这也不是他们所期望的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5444935|应避免打破后退按钮。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

Breaking the back button is like breaking the brake pedal in a car. Users expect it to always work and when it suddenly doesn't mayhem ensues. The back button might be the most used UI feature in a browser so altering its behavior it any way can, at best, do no good, and, at worst, result in user confusion and abandonment (or increased customer support costs). Even if it takes the user right back to where they were that's not what they were expecting.

Breaking the back button should be avoided.

blocks|key|4258321|text|在用户正在进行测试的站点(一些银行网站)，打破后退按钮是很重要的。一般来说，这不是个好主意。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

It is important to break the back button at sites where user is taking quiz, some banking sites. Generally , not a good idea.

blocks|key|5445034|text|在某些情况下，按下后退按钮可能是可以的，但它几乎总是不必要的。我在多步表单中看到了很多，你可以从一个页面到下一个页面发布。在这个实例中，您应该做的是从表单页面(1)发布到另一个页面(2)，该页面(例如)将内容存储在会话中，然后重定向回另一个页面(3)。当用户按下后退按钮时，他们将从(3)返回到(1)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5445035|即使使用RIA，您也可以使用URL+/锚(即page.html#section)并监视它们的变化。Gmail为不同的“页面”(如收件箱、撰写、设置等)做这件事。如果你想实现它，关于堆栈溢出的问题会帮助你。|offset|length|style|CODE|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1078501/keeping-history-of-hash-anchor-changes-in-javascript^0|0|M|H|2G|9|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@$D|S|E|T|1|U]]|A|$]]]|H|$I|$5|J|K|L|A|$M|N]]]]

Breaking the back button may be OK in some cases, but it is almost always unnecessary. I've seen it a lot with multi-step forms where you post from one page to the next to the next. What you should do in this instance is from your form page (1), post to a different page (2) that (for example) stores stuff in the session, then redirect back to another page (3). When the user presses the back button they will go from (3) back to (1).

Even with RIAs you can uses URL hashes/anchors (i.e. <code>page.html#section</code>) and monitor them for changes. Gmail does this for the different 'pages' like Inbox, Compose, Settings etc. <a href="https://stackoverflow.com/questions/1078501/keeping-history-of-hash-anchor-changes-in-javascript">This question on Stack Overflow</a> will help if you if you want to implement that.

blocks|key|4258226|text|它“越来越普遍”的主要原因是一些RIA框架不支持back按钮，或者要求您积极考虑如何将它的使用合并到应用程序中。不过，大多数框架确实提供了一些导航支持，比如Silverlight+3's对框架和页面控件的支持，您只需要知道如何有效地使用它。在Windows+7应用程序中也使用相同的导航框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://www.silverlightshow.net/items/The-Silverlight-3-Navigation-Framework.aspx^0|2M|7|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

The main reason why it is "increasingly common" is that some RIA frameworks do not support the back button or require you to actively think about how to incorporate it's use into your application. Most frameworks do offer some support for navigation though, such as Silverlight 3's support for <a href="http://www.silverlightshow.net/items/The-Silverlight-3-Navigation-Framework.aspx" rel="nofollow">Frames and Page controls</a>, you just have to know how to use it effectivly. The same navigation framework is used in Windows Phone 7 applications.

blocks|key|5445090|text|研究表明，在使用浏览器时，几乎有1/3的点击是在“后退”按钮上(“不要让我思考”)。老实说，我不相信有什么好的理由来阻止后退按钮的工作。人们应该能够浏览您的网站，但他们认为适合。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Studies have shown that almost 1/3 of clicks when using the browser is on the back button (from Don't Make Me Think). I honestly don't believe there is ever a good reason to stop the back button from working. people should be able to navigate around your site however they see fit.

blocks|key|5445162|text|我的经验是，除非您在浏览器(如上面提到的silverlight+)的上下文中使用包含的框架(如应用程序)，而且具有清晰、合适的导航，否则开始使用默认功能进行修改并不是一个好主意。在我见过它使用的情况下，另一个浏览器与javascript或会话不兼容时，几乎总是会出现问题，不能总是正确地保存，而且当有人“意外”按下按钮时，事情往往不会像预期的那样继续下去。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

My experience has been that unless you are using a contained framework such as an app WITHIN the context of a browser (like silverlight mentioned above), and have clear, suitable navigation in place, it is just not a good idea to start monkeying around with default functionality. In cases where I have seen it used there have almost always been problems with another browser being incompatible with the javascript or a session not always saving correctly, and when someone "accidentally" hits the button things tend to not continue on as expected.

blocks|key|5445310|text|不要忽视“频繁”用户按“后退”按钮的情况，或者说“打破”按钮不是一个“好主意”，我想提出一个不同的建议:后退按钮应该在用户到达他们现在的位置之前把用户带到某个地方。在很多情况下，它更有意义，更有用的做法是不使用一个链接-单击上(可能更容易实现)。例如，以浏览相册为例。用户点击一次选择相册，就会显示出缩略图。在缩略图上的另一个点击显示该图片与下一个/先前的链接。此时，用户浏览相册。当它们完成后，它们单击“后退”。在这一点上，回到缩略图比以前的图片更方便和直观。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5445311|简而言之，back按钮应该做一些事情，但是确切地说它应该做什么取决于应用程序。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

Not to discount how "frequent" users press the back button, or that it simply isn't a "good idea" to "break" it, I would offer a different suggestion: The back button should take the user to somewhere before the user got to where they are now. In a lot of cases it makes more sense and is more usable to not take them one link-click back (and may be much easier to implement). For example, take browsing a photo album. The user make one click to select the album, is presented with thumbnails. Another click on a thumbnail shows that picture with next / previous links. At this point the user navigates through the album. When they're finished, they click back. At this point, it's more convenient and intuitive to go back to the thumbnail than to the previous picture.

In short, the back button should do something, but exactly what it should do depends on the application.

It is increasingly common for "rich" applications to break the back button. I've always held that this was bad form but perhaps that view is outdated?

Is it ever Ok to break the back button? And if so, what are the criteria?

<hr>
Edit: 
To clarify I was more referring to applications where clicking the back button basically just sends you right back where you were. Effectively disabled but not in any way harmful to press.

'Back button' functionality, how important is it?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

“富”应用程序打破后退按钮的情况越来越普遍。我一直认为这是一种糟糕的形式，但也许这种观点已经过时了？打破后退按钮可以吗？如果是的话，标准是什么？编辑:为了澄清，我更多的是指的是应用程序，点击后退按钮，基本上就是把你送回原来的位置。有效的残疾，但没有在任何方面有害的新闻。

问‘黑按钮’功能，它有多重要？
EN

回答 9

Webmasters Stack Exchange用户

Webmasters Stack Exchange用户

Webmasters Stack Exchange用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问‘黑按钮’功能，它有多重要？EN

回答 9

Webmasters Stack Exchange用户

Webmasters Stack Exchange用户

Webmasters Stack Exchange用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问‘黑按钮’功能，它有多重要？
EN