Tag Info

New answers tagged

0

I agree that in general hiding the link is preferred. But in this case I'd make an argument for keeping the links but greying them out. You have a bunch of possible links on any post and a bunch of different states with different options available. If you hide the links, as you have in your screenshots, the layout of each set of links is very different for ...


0

You're right to consider removing the unactionable links (as lzhaki has said) this will only confuse users. I also agree that it's a little more complicated when an action can activate the links. In that instance my suggestion would be to keep the links visible but greyed out, this at least suggests that there may be an available action that can activate ...


2

There isn't much point cluttering the interface (visual noise) with actions that cannot be performed. It violates quite a few UX heuristic. Obviously when an action can be unlocked via user action, orientation comes to mind (although it may still be worth hiding the locked actions so their introduction to the interface will draw attention). Aspects such as ...


0

Make the change option explicit Eg if option 1 is the existing choice and the are 4 other options Layout would be You current choice is Option 1 (x) Change to..... Option 2 ( ) Option 3 ( ) Etc Makes change explicit and reduces cognitive load How you choose to present will depending on your programming overhead(eg sort order etc) Also by making ...


0

I'm not sure I have understood your problem, anyway I see 2 solutions: Use a checkbox like confirm option 2, the user will be forced to check it (modern browsers will add a prompt if the required attribute is present) . This is seen on many website where you have to accept Terms of Service to complete an order, etc. Use <input type="submit" ... > or ...


0

If you need the user to change the selection, disabling the save/submit when the user wants to retain the selection may not be the optimal experience. Some alternate strategies would be: Make the button show Save, and then Submit so that if the user wants to retain option 1 there is an explicit confirmation. If the user wants to change to option 2 there ...


1

This is OK and acceptable behavior. BUT: common alternatives are: Allow the user to press save. Disabled buttons can be frustrating to users, and after all, there is no harm done by just re-saving the existing option. This also fixes an awkward case where the user selects Option 2 (enabling the save button) and then re-selects option 1 (do you then ...



Top 50 recent answers are included