Depends on the scenario, js can do data checks just fine, so, it really
depends, but onsubmit is a popular way to use. Server sided submits for
checking, and loads the result either if it validates or not, is uses the
client bandwidth regardless to do a page request and page serving, there's
timing and server load, while using it client sided, there isn't any
delays due to session transactions, if the user makes a mistake, it's let
known right away and addressed right there. You could do a browser check
server sided in order to spot older browsers and do server sided for them,
else, use js.
Danny
On Sun, 19 Jun 2005 15:18:08 -0700, <te***@yahoo.com> wrote:
I usually use the onSubmit event to validate form because in case an
error is generated (not because user misses a field), the submit will
continue. Current I have a form in which I have to do a hidden iframe
background process to validate server side. If sucess then the iframe
page would generate the script to subit form. I don't like it because
if there's an error, the form won't be submitted at all even though
it's not the user's fault. I'd like your ideas on how to handle form
validations. Thanks.
--
Using Opera's revolutionary e-mail client:
http://www.opera.com/mail/