用户登录后在新窗口中打开用户会话而不使用浏览器菜单有什么好处吗？
一些网站（我见过不少银行网站这样做）会让用户从其主网站登录，然后当用户单击登录时，将打开一个弹出窗口，其中包含用户会话。此会话通常不包含任何典型的浏览器菜单或 URL 地址栏。
我从用户体验的角度了解到，这不是一个好的做法，因为用户渴望熟悉感，失去后退按钮和文件菜单等舒适感可能会令人不快。
谁能告诉我这种做法的实际好处是什么？
Some websites (I have seen quite a few bank websites do it) will have a user log in from their main website and then when the user clicks on log in, a pop window will open with the user session. This session will usually not contain any of the their typical browser menus or url address bar.
I have read from a user experience perspective that this is not good practice because users crave familiarity and losing comforts such as the back button and file menu can be off putting.
Can anyone tell me what the actual benefits of this practice are?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
当应用程序变得足够丰富，足以与桌面应用程序竞争时，在没有浏览器控件的情况下在自己的页面中打开 Web 应用程序就开始有意义，而不是用户浏览的一堆页面，每个页面的输入最少。可用性优势包括：
未保存的用户输入字段不会因导航到另一个页面而丢失。在普通的 Web 应用程序中，用户在查看任何其他页面之前必须完成对一个页面的输入，本质上构成了一个完全由模式对话框组成的应用程序。
退出应用程序是明确的，因为单击退出/注销按钮可以关闭窗口。 “后退”按钮历史记录列表中没有留下任何页面，不会给人留下会话仍在进行且输入仍被接受的错误印象。这也可能具有安全优势。
用户的“工作空间”由应用程序控制，其设计可确保用户可以随时访问他们正在处理的任何内容。在普通的 Web 应用程序中，单击“返回”，然后单击链接“删除”历史列表，导致无法轻松访问用户可能正在处理的页面。
Web 应用程序必须足够丰富以支持所有需求，这样用户就不会错过浏览器控件。例如，它应该具有打印、查找、文本大小等控件。这些控件的外观和感觉应该与典型应用程序（例如浏览器）类似（例如，位于大致相同的位置，可能在“文件”-“编辑”-“查看”中）下拉菜单）。
用户失去了对浏览器环境的熟悉度，而是用它来换取对桌面环境的熟悉度——大多数桌面应用程序都没有后退按钮，但效果很好。隐藏浏览器控件不仅可以阻止用户做任何破坏性的事情，例如从收藏夹中打开新页面，而且还向用户发出信号，表明他们不再处于浏览器环境中，因此应用新规则。为应用程序提供桌面外观和感觉在这方面也会有所帮助。
该应用程序应该独立于单个页面中，以便不需要分页。但是，如果应用程序对此过于复杂，我建议您在自己的窗口中打开任何新页面< /a> 使应用程序与其自身保持一致，并与桌面应用程序保持一致。不要将页面后退导航模型与在新窗口中打开模型混合在一起，否则用户会对如何访问之前的页面感到困惑。避免在新窗口中打开网页的可用性指南实际上是不混合模型的指南。
Opening the web app in its own page with no browser controls starts making sense when the app becomes rich enough to rival a desktop application, rather than being a bunch of pages the user browses with minimal input to each. Among the usability advantages:
Unsaved user input to fields cannot be lost due to navigating to another page. In an ordinary web app, the user is trapped in completing input to one page before looking at any other, in essence constituting an application made entirely of modal dialog boxes.
Exiting the app is unambiguous, since clicking an Exit/Logout button can close the window. There are no pages left behind on the Back button history list to give the false impression the session is still going and input is still accepted. This may also have security benefits.
The user’s “work space” is control by the application, which can be designed to ensure the user has ready access to anything they’re working on. In an ordinary web app, clicking Back then clicking a link “prunes” the history list, resulting in the loss of easy access to pages the user may have been working on.
The web app must be rich enough to support all needs so the users won’t miss the browser controls. For example, it should have controls for Print, Find, text size, etc. These should have a look and feel similar to typical apps, such as browsers (e.g., be located in roughly the same place, perhaps within File – Edit – View pull-down menus).
User’s lose the familiarity of the browser environment, but trade it for the familiarity of a desktop environment –most desktop apps lack Back buttons and that works fine. Hiding the browser controls not only discourages the user from doing anything damaging, like opening a new page from Favorites, but also signals to the user that they’re no longer in a browser environment, so new rules apply. Giving the app a desktop look and feel would also help in this regard.
The app should be self-contained in a single page so that paging is unnecessary. However, if the app is too complex for this, I recommend you open any new page in its own window so that the app is consistent with itself and consistent with desk-top apps. Don’t mix a page-back-forward navigation model with an open-in-new-window model or else users will get confused on how to get to previous pages. The usability guideline to avoid opening a web page in a new window is really a guideline to not mix models.
一个可能是隐藏 URL，这样用户就无法摆弄它，尽管经验丰富的黑客可以轻松修改它。我的银行隐藏了后退按钮，但我想这是有原因的，因为按退格键或鼠标上的后退按钮会使我的会话过期。我也看到菜单被禁用，阻止用户打印、查看源代码、脱机工作等。我猜他们几乎是在试图在网络浏览器中模仿桌面应用程序。
One could be hiding the URL so users can't fiddle with it, though experienced hackers could easily modify it.. My bank hides the back button, but I guess for a reason since pressing backspace or the back button on my mouse expires my session. I've seen menu's disabled as well, preventing users from Print, View Source, Work Offline and the like.. I guess they're almost trying to mimic a desktop application in a web browser.
我的假设是他们的应用程序在前进和后退按钮方面严重失败。他们宁愿启动一个前进和后退更难访问的窗口，而不是在一个能够优雅地处理前进和后退的框架中编写应用程序。
当然，键盘快捷键可能仍然有效，因此当银行丢弃数据时，用户仍然会感到惊讶。
好处是用户不知道他们实际使用的是哪个网站！
恨。
My assumption is that their application fails badly with the forward and back buttons. Rather than write an application in a framework that handles forward and back tastefully, they'd rather just launch a window where forward and back are harder to get to.
Of course, keyboard shortcuts probably still work, so users can still be surprised when their bank throws away their data.
And the bonus is that users haven't got a clue which website they are actually using!
Hate.
对于我的信用合作社，我的帐户访问是通过不同的组织和不同的网站 secure.fundsxpress.com
但是，我的后退按钮仍然有效。信用合作社的标志仍然存在于框架中。
为了回答您的问题，一个单独的弹出窗口可能会矛盾地使银行交易感觉比仅使用浏览器窗口更安全。当然，银行客户必须信任网站和银行。
你是对的，大多数人不喜欢弹出窗口。一般来说，应该避免弹出窗口。
With my credit union, my account access is through a different organization and a different web site, secure.fundsxpress.com
However, my back button still functions. The credit union logo is still there in a frameset.
To answer your question, a separate pop up window can paradoxically make the bank transactions feel more secure than just using a browser window. Of course, the bank customer has to trust the web site and the bank.
You're correct that most people dislike pop up windows. Pop up windows are to be avoided, generally.