We try to place as much error checking client side - since the order (as it's currently built) does not touch the server until it's being submitted (and many of you charge just before this moment, or as part of it) an error could prove more than inconvenient....
We try to maintain some semblance of consitency with error checking (trying not to suddenly alter requirements mid-leap, so to speak); occasionally some registries make this rather difficult (and more so, now that thick registries seem to be the norm) Charles Daminato TUCOWS Product Manager [EMAIL PROTECTED] On Thu, 28 Feb 2002, Mark wrote: > There are a couple of problems with doing that. > > First, it means that the pages would not be compatible with all browsers, > specifically those that don't support Javascript. > > Also, it would move the verification logic to the client side, rather than > the server, so when the logic changes, it would require an upgrade of the > client on your end. For any resellers who have heavily customized the > templates, this would be a nightmare. > > IMO, all error checking, should be done server-side, rather than client-. > > Take care, > Mark. > > On Wed, 27 Feb 2002, Biz-Lists wrote: > > > Using the Quick Start interface, whenever I forget to fill in a required > > field and I hit submit - I get an error message (as it should be). When I > > hit back on the browser the form is completely empty requiring me to retype > > all of the information. > > > > My question is this - is there some other proceedure that I should be using > > other than the back button so the form will not be cleared??? > > > > Here is my suggestion. Using something as simple as JavaScript the form > > could be checked before it is submitted. I have wasted a lot of time > > retyping information - the original mistake is mine but it seems like the > > interface could be made a little more user friendly and forgiving. > > > > CJS > > > > > >
