Inline validation is the best way to go, but the user could still not enter anything and see that the form is "disabled" and wonder why. but that is a better trade off then having a button they can press which doesn't work. better to prevent errors then allow them and then message about them later. If really concerned, you could put a message next to the submit button stating that the form must be filled out to enable the button.
On Thu, Jul 3, 2008 at 12:46 PM, Robert Hoekman Jr <[EMAIL PROTECTED]> wrote: > > > > One way to prevent this would be to disable the button and give it > > that grayed out visual treatment until they enter a dollar amount but > that > > would mean that when they arrive at the page they'll see a "broken" > button. > > > Agreed, assuming most people actually look at the button prior to > completing > the form. > > I think I'd lean towards showing an enabled button and then > > giving a "You did not enter a dollar amount." error message if they > pressed > > it. I'd love to hear your thoughts. > > > > Definitely—inline validation, prior to to the button click, is ideal. Not > easy to code, but ideal. And of course, the messages should tell users how > to do things correctly rather than just accusing them of doing something > wrong (e.e. "Your email must be in the form '[EMAIL PROTECTED]'"). > > -r- > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... [EMAIL PROTECTED] > Unsubscribe ................ http://www.ixda.org/unsubscribe > List Guidelines ............ http://www.ixda.org/guidelines > List Help .................. http://www.ixda.org/help > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
