自动重定向用户或向他们显示有错误的请求页面哪个更好？
给定一个 Web 应用程序中的场景，用户必须执行 X 操作才能继续访问 Y，但 Y 的链接始终可用，我们当前正在讨论在用户尝试导航到页面 Y 时重定向用户的两种方法：
- 显示带有消息和 链接回 X。
- 自动重定向到 X，但是 显示错误消息叠加层 在指示的重定向之后 为什么他们被重定向。
哪个更用户友好或更好的用户体验，为什么？
Given a scenario in a web application where the User has to do X before they can proceed to Y, but where the link for Y is always available, we are currently discussing two ways of redirecting the user if they try to navigate to page Y:
- Display page Y with a message and a
link back to X. - Redirect to X automatically but
display a an error message overlay
after the redirect that indicates
why they were redirected.
Which would be more user-friendly or a better user experience and why?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
或者，您可以使用第三个选项：
当用户单击链接时，显示一个对话框，解释错误和建议的操作过程，然后提供一个尽管出现错误仍继续的链接以及重定向到推荐页面的链接/ 行动。
Or, you could use a third option:
When the user clicks the link, display a dialog which explains the error and the recommended course of action and then provides a link to continue despite the error as well as a link to redirect to the recommended page / action.
嗯，从可用性的角度来看，我认为只向用户实际显示那些在上下文中有意义的选项是最有意义的，即只要 X 未满足，就根本不显示到 Y 的链接。
也许，如果您不想完全删除链接文本，只需删除链接并保留文本（并说明为什么当前是这种情况）直到填写 X 为止？
Hm, from a usability perspective I'd say it makes most sense to only actually display those options to the user that make sense in the context, i.e. not showing the link to Y at all as long as X is not fulfilled.
Maybe, if you don't want to drop the link text entirely, just remove the link and keep the text (and state why that is currently the case) until X has been filled out?
阅读您对项目 A 和项目 B 的评论。
我的想法如下：
您有两个链接，链接 X 和链接 Y。
对于项目 A，链接 X 和链接 Y 显示为普通超链接，一切都很好。
对于项目 B，链接 X 显示为普通超链接，但将链接 Y 呈现为带有特殊指示性图标的文本/超链接，并且当用户将鼠标悬停在其上（而不是单击）时，显示弹出窗口/工具提示解释原因。
这里的想法是减少鼠标点击（如上所示，无点击且无重定向）并节省页面空间/屏幕空间（显示鼠标悬停时的原因）。
此外，您可以在页面中放置一条说明，说明用户必须完成链接 X 中的所有内容才能继续链接 Y。
Read you comment about Item A and Item B.
My idea below:
You have two links, Link X and Link Y.
For Item A, Link X and Link Y appear as normal hyperlinks, all good.
For Item B, Link X appears as normal hyperlink, but render Link Y as text / hyperlink with a special indicative icon, and when user hovers over it (not click), display a popup / tooltip explaining the reason.
The idea here is to reduce mouse clicks (as you can see above, no clicking and no redirect) and also saving page space / screen estate (display the reason when mouse hover).
In addition, you may put in an instruction in the page stating that user must complete all the things in Link X to proceed to Link Y.
我认为，如果他们没有在 X 上输入所需的所有信息，您可能希望将它们放回 X 上，并提供一些清晰可见的指示符来表明他们没有做什么。当然，您不应该在没有填写所有信息的情况下让它们保存，但有时服务器验证会失败。
最终，虽然是一打六，另一打六打，我已经看到了这两种情况。
如果他们必须在 y 之前执行 x，为什么 y 的链接始终可用？
I think if, say, they didn't enter all the info they needed on X, you might want to put them back on X with some clearly visible indicator of what they didn't do. Of course, you shouldn't let them save without filling out all the info, but sometimes server validation fails.
In the end though its six of one, half dozen of the other, and Ive seen it both ways.
If they have to do x before y, why is the link to y always available?
我会采用第二种方法。因为我们很可能知道用户会返回上一页，检查其他链接或检查可能导致问题的原因。所以，这种方式为用户节省了一些时间。
I would go with the second approach . Because most probably we know that the user will return to the previous page a check other links or check what might have caused the problem. So, this way way saved some time for the user.
除非合适，否则我不会允许用户导航到 X。
但是，既然您询问用户友好性，我猜您的用户可能会对在页面 X 上感到困惑，因为他们认为自己在 Y 上（而且他们甚至不会注意到浏览器顶部的 100 像素栏，除非它是红色的并且闪烁），所以我会选择一个完全空白的错误页面（没有导航），只有一条清晰的消息和一个链接。类似于简单的 HTTP 404 错误页面。
I would not allow the user to navigate to X unless it's appropriate.
However, since you ask about user-friendliness, I guess your users could get confused about being on page X when they think they're on Y (and they won't notice even a 100px bar on top of their browsers unless it's red and blinking), so I'd go for a totally blank error page (no navigation) with just a clear message and a link. Something similar to a simple HTTP 404 error page.
这取决于用户的期望是什么。
如果用户可以收集他们被重定向的原因（典型的示例是“您需要登录才能查看此页面”），请执行此操作。
如果用户可能对为什么看到他们没有要求的内容感到困惑，那么向他们展示他们要求的内容以及适当的限制和错误消息。
It depends on what the user's expectation is.
If the user can gather why they got redirected (the classic example being "You need to log in to view this page"), do that.
If the user is likely to be confused why they are seeing something they didn't ask for, then show them what they asked for with the appropriate limitations and error messages.