RE: [PHP] Re: your method for validating forms
| From: | Robert Cummings | Date: | Thu, 02 Oct 2003 19:14:55 +0000 |
| Subject: | RE: [PHP] Re: your method for validating forms | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-164811@lists.php.net to get a copy of this message | ||
Heeeeeeeeeeey, a great little response like this to see an alternative
to a popup and no link for us to check it out *pffffffffffft* Where'd
you learn your posting manners? Were you brought up in a web barn?
*grin*. Wouldn't happen to know the URL still would ya?
Cheers,
Rob.
On Thu, 2003-10-02 at 12:23, Chris W. Parker wrote:
> Chris Shiflett <mailto:shiflett@php.net>
> on Wednesday, October 01, 2003 11:18 PM said:
>
> > There are definitely benefits to saving the extra request and response
> > necessary to properly display errors, but I'm not so sure I would
> > count usability as one of them. In addition, the user's perception of
> > the site's general quality and professionalism may be a concern, and
> > a JavaScript popup certainly doesn't improve this.
>
> I went to an ecom site today that used js validation but in a very slick
> way. There were no popups to be seen. Instead, when I tried to add a
> product to my cart without specifying some attributes a little red
> message magically appeared on the page that said "Please choose a
> color".
>
> A client-side validation class would be usable imo if it doesn't utilize
> popups. Not being experienced with js I can imagine that not using
> popups and still warning the customer of a mistake would be complicated.
>
> I prefer server-side but that's mainly just because I don't like js.
>
>
>
> Chris.
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com
|
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting |
| a powerful, scalable system for accessing system services |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for |
| creating re-usable components quickly and easily. |
`------------------------------------------------------------'