Tag Info

Hot answers tagged

14

Generalising between platforms I would go with the following basic guidelines, they further emphasise a disabled field with a grey background. Normal (with a value) Black text, white background, black border. Normal (with a placeholder) Grey text, white background, black border. Disabled Grey text, slightly lighter grey bg, grey border. E.g.


7

In most cases, forms are made of native elements and the look and feel is therefor (ideally) determined by the operating system. Mac OS has a different way of showing something is disabled if you compare it to windows. Here are two text fields of Windows XP and Mac OS X with native behavior: vs. I would advice you not to change this behavior for several ...


6

You should not show controls to the user if they can not interact with them. It will cause problems like frustration, doubts and may be even leaving the process altogether. If the user finds a control that he can't interact with, first is going to look for an explanation of why. Once he doesn't find that answer, he may feel that missed a step before, and ...


6

Some things I have seen done before in this scenario: Make placeholder text green instead of grey (user input is in black) Placeholder text is in italics (user input is in normal text) Put angle brackets around text, eg. < your name here >. (This one is somewhat "technical", i.e. something a programmer is more likely to understand) I would suggest ...


5

Either way is fine. Of course, replacing the text with "Nothing to Paste" is much more clear and understandable than just disabled "Paste" menu entry, which is good for UX. However it seems to be standard to leave the disabled entry unchanged, like on Windows explorer, you won't find a dynamic disabled paste entry. This way is also friendly for UX because ...


4

I don't think that both options should be visible at the same time. Having a control that allows to view one option at a time greatly simplifies interface and reduces cognitive load. You need to make a decision which option should be a default one based on business requirements and past usage analytics. I believe tabs allow to solve this problem quite ...


2

Based on the constraint that you want to keep both sets of fields visible and indicate that they are both usable at any point, you could wrap them in a radio button group if it's not too confusing for your users, since what you're trying to say to the user (if I'm interpreting you correctly) is that they can use a preset, or they can set a specific range. ...


2

There are several reasons that if your facetted search is very open, more like a network of combined selections, that you should leave empty filters visible. Consistency You are better off disabling the filters so the interface retains consistency throughout the interaction. If there are always the same set of filters then the user can learn the interface ...


1

Disable option tells you that you are not eligible to access this feature because of 1: f permissions 2: or they are dependent on another action & gets invoked after an action. You can keep them disable and give an explanation on hover[not mandatory]


1

People who are flicking through navigation like that are expecting to click in the same place all the time. The simple fact is that most users don't look when they are clicking "next" on each page / screen. If you start removing items from your navigation because they don't apply for that particular page, the other navigation links will move relative to ...


1

I think if the context is easily understood, disabling without hints of why, is fine. Remember Balloon help in MacOS? Apple encouraged us to write balloon help for disabled items way back from 1991 and forward. Microsoft did not. But as said above, tool tips only work if you have the hover event, not for touch. For more complex scenarios, explanation why ...



Only top voted, non community-wiki answers of a minimum length are eligible