RobG wrote: > On Mar 30, 7:06 am, "Gareth Evans" <[EMAIL PROTECTED]> wrote: >> Useful trick >> Better than a keypress handler! > > But lousy for accessibility. > > Many users will find a form with no submit button confusing. Why not > just put a visible submit button on the form? Give it a visual label > of "Go", "Search", "Send", "Logon" or whatever action will be carried > out, but put something there so that users know what will happen when > they submit the form.
I think you missed something that I said along the way. The forms I was talking about have <input type="button"> controls. So to the user it looks like there are submit buttons. Just multiple buttons. These buttons are observed with onclick handlers. The problem that I wanted to avoid was having one submit button mixed in with the inputs because submits are treated differently than inputs by browsers (wrt to whether or not they submit the form or not). It was simpler to make them all inputs and not worry about it. But in that case we lost the 'enter' submission thingy. > Give users a choice of whether they submit the form by pressing enter > or by clicking a button - I prefer to use an enter key, but many users > prefer to use mouse clicks. That's what I was trying to do, but at the same time make it easy for my form designers so they wouldn't have to do one thing for submit inputs and another for button inputs. -- Michael Peters Developer Plus Three, LP --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
