2

I'm building a store-like site and users can publish their own ads and I was wondering if not showing the submit button until the form has been completeley validated is a good idea, for example if the client didn't input his name or his address the submit button won't be visible.

What do you think?

  • 1
    possible duplicate of Disabling submit-button until the user has completed the form – tohster Feb 23 '15 at 22:39
  • 1
    It might be a duplicate but my question is more oriented towards displaying the submit button or not, instead of showing it disabled. – octohedron Feb 23 '15 at 22:47
  • It's similar, but I agree that the change in the focus changes the answers. @Gazta please make this somewhat more explicit in your question to avoid confusion. – JohnGB Feb 24 '15 at 10:02
4

Usually the primary active element (in this case a 'Submit' verb button) affords the user a clue about what to do.

A disabled button is encoded with two dimensions: what do do and that you cannot do it yet. While this might also be confusing it does not leave as much to mystery. It also might not appear as a mistake.

The big question to ask is: Why? I do not think you gain much from hiding the element. It doesn't tell anything (affording) the user useful information.

The best way to go is label the required elements (or form if all are required clearly) to avoid a mistake, then handle the error properly when/if it occurs. Avoid uncommon design patterns that yield little benefit.

Check out Design Heuristics for additional info and guidance.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.