No matter what you do to visually imply something is disabled, old/inexperienced/hasty users will lose time trying to comprehend that the form looks like a form but it isn't.
"Comment on this article by signing in or registering" which links to the login and registration form, once they have registered they should be directed back to the comment form so they can leave a comment.
Leaving the form visible but inactive would make the user think they have to click somewhere special to activate it.
Disabling them saves the user from effortlessly looking for functionality she knew to exist before. So in general, hiding something completely from view just generates frustration. Remember the dynamically populated menus in Office 2000 to 2003? Then you know what I mean (cf. Jensen Harris' blog posts on that topic).
I suggest you should disable them and make it clear in what states they are available and how to achieve that.
In some cases, however, such as the application we are developing right now, functionality being there or not depends more on the user's permissions than on the current state of the program. In such cases it can be helpful to just hide things that shouldn't be accessible since users never get to the point where they could use the controls. Simply because they're lacking privileges. See for example Stack Overflow's moderation tools which are accessible once you get above 10k rep but are never shown before, not even as disabled.
发布评论
评论（6）
如果您不想让用户知道有评论表单，您应该隐藏它。
如果您希望用户知道有一个评论表单，但他们（尚未）可用，您应该禁用它（将其灰显）。
您可能有充分的理由想要隐藏而不是灰色。例如，如果您正在对接口进行安全调整。
If you don't want the user to know there is a comment form you should hide it.
If you want the user to know there's a comment form, but it is not (yet) available to them, you should disable it (gray it out).
There are good reasons why you might want to hide instead of gray. If you are security-trimming the interface, for example.
变灰。
您希望用户知道有哪些选项可用。如果它们被隐藏，用户可能永远不知道存在其他设置。
编辑：
我想我想说的是，如果你真的应该隐藏一个你会知道的选项。 IE 间距问题、安全问题等等。
Gray out.
You want users to be aware of what options are available. If they're hidden a user may never know that additional setting exists.
EDIT:
I guess what I'm trying to say is if you really should hide an option you'll know. IE spacing issues, security, whatnot.
无论您采取什么措施在视觉上暗示某些内容被禁用，老用户/缺乏经验/仓促的用户都会浪费时间试图理解表单看起来像表单但事实并非如此。
我会传达一个明确的信息。
No matter what you do to visually imply something is disabled, old/inexperienced/hasty users will lose time trying to comprehend that the form looks like a form but it isn't.
I would go with a clear message instead.
将它们灰显。如果他们点击它们，请提供一条消息，说明为什么他们不可用。
gray them out. if they click on them provide a message stating why they are unavailable.
隐藏表单并提供一条消息，例如：
“通过登录或注册对本文发表评论”，该消息链接到登录和注册表单，注册后，他们应该返回到评论表单这样他们就可以发表评论。
让表单可见但不活动会让用户认为他们必须单击特殊的地方才能激活它。
Hide the form and provide a message such as:
"Comment on this article by signing in or registering" which links to the login and registration form, once they have registered they should be directed back to the comment form so they can leave a comment.
Leaving the form visible but inactive would make the user think they have to click somewhere special to activate it.
禁用它们可以使用户不必费力地寻找她以前知道存在的功能。因此，总的来说，将某些东西完全隐藏起来只会产生挫败感。还记得 Office 2000 到 2003 中动态填充的菜单吗？那么您就知道我的意思了（参见 Jensen Harris 的 博客文章< /a> 该主题）。
我建议您应该禁用它们并明确它们在什么状态下可用以及如何实现这一点。
然而，在某些情况下，例如我们现在正在开发的应用程序，功能是否存在更多地取决于用户的权限，而不是程序的当前状态。在这种情况下，隐藏不应该访问的内容会很有帮助，因为用户永远不会到达他们可以使用控件的程度。很简单，因为他们缺乏特权。例如，请参阅 Stack Overflow 的审核工具，一旦您的代表次数超过 10k，就可以使用这些工具，但以前从未显示过，甚至没有被禁用。
Disabling them saves the user from effortlessly looking for functionality she knew to exist before. So in general, hiding something completely from view just generates frustration. Remember the dynamically populated menus in Office 2000 to 2003? Then you know what I mean (cf. Jensen Harris' blog posts on that topic).
I suggest you should disable them and make it clear in what states they are available and how to achieve that.
In some cases, however, such as the application we are developing right now, functionality being there or not depends more on the user's permissions than on the current state of the program. In such cases it can be helpful to just hide things that shouldn't be accessible since users never get to the point where they could use the controls. Simply because they're lacking privileges. See for example Stack Overflow's moderation tools which are accessible once you get above 10k rep but are never shown before, not even as disabled.