Hi Tee,
What John is saying is that AJAX is JavaScript yes, but it can also make
calls to the server (using the XMLHttpRequest object) thus it validates
using server-side technologies such as PHP. But what is misleading is that
validation using AJAX can be disabled quite easily simply by
Why client-side *VS* server side? Why *versus*?
They must work together.
1. We cannot dismiss server-side validation for security reasons.
So, server-side validaion should stay.
2. Client-side script is usable. It checks the form before submission,
saves user's time and improves user
Hi Matt, thank you very much! Your JS library looks very interesting
and I certainly will play with it. I see that the radio group has not
been implemented, is this something coming out soon?
The web form has radio buttons with multi-selection options.
Cheers,
tee
On Feb 12, 2008, at
+1 on this.
I am no l33t h4x0r (by any stretch of the imagination), but even I know I can
easily circumvent client-side validation for nefarious purposes in at least
the following ways:
1. save the form onto my drive, remove all js and submit the form to your
server url with pretty much any
It should be made clear that there really is no such thing as Client
Side Validation. What we are talking about here is client side form
assistance. The goal of validation is to make 100% sure that the data
you are recieving is of the correct type, and contains no extraneous
data or security
Matt Fellows wrote:
What John is saying is that AJAX is JavaScript yes, but it can also
make calls to the server (using the XMLHttpRequest object) thus it
validates using server-side technologies such as PHP.
What you describe is what AJAX actually is; however, the term is often
misused to
Hi Tee,
It sure is, I have actually implemented it locally but a bit of testing is
needed. It was more a test-of-prinicple kind of thing that actually turned
out useful.
So we don't move off topic however, I will reply to your email privately
about the library instead of the WSG list.
Cheers,
The sever side validations must be done even if the validations are done at
client side too.
this is because it is highly likely to crash if the user has turned off
Javascript
Sajan
On Feb 12, 2008 4:43 PM, tee [EMAIL PROTECTED] wrote:
Hi, I have a question about server-side vs client-side
Hi Tee,
I suppose I can turn off the server-side validation if client-side
validation is used, but I am concerned with the accessibility issue
You can have it both ways. The JavaScript can work before anything is even
submitted to the server (very AJAXy) so the server-side validation isn't
You should always do server side validation. Implementing client side
validation does not affect this at all.
On Feb 12, 2008 4:08 PM, Sajan Franco [EMAIL PROTECTED] wrote:
The sever side validations must be done even if the validations are done
at client side too.
this is because it is
In my experience client-side validation works fine with screen readers but
you need to be careful how you present any error messages. It is
increasingly common to see them slid in silently, and this is a big problem
not only for screen reader users but also for magnifier users because they
are
A website I was working on, client wants client-side
validation, something fancy, something Ajax.
The whole point of AJAX is that it's *not* client-side. It's both. So
your client is a little confused if they said that.
Thank you all for the great response.
I thought client-side validation will conflict (and confuse user) with
server-side - I thought that when a user get passed the client-side
validation and click submit, another error message may pops up to warn
him the telephone number format he
tee wrote:
Hi, I have a question about server-side vs client-side validation. I
always use a same PHP form script that works really great and it's
server-side validation using condition and requirement, and I like the
feature better than client-side's. A website I was working on, client
wants
14 matches
Mail list logo
