Client-Side Error Trapping on City and State

hi,

We recently had a customer who typed "BETHESDA, MD" into the zipcode field of the checkout form.

The postal code field did not try to "auto-find" the city/state, assuming because it was not a valid postal code, and the customer also did not click the "Go" button next to the field. They proceeded to fill out and submit the form.

The client-side error-trapping did not catch the fact that "city" and "state" were unpopulated, but server-side error-trapping did catch this.

so my questions are:

1) Why no client-side error-trapping for postal codes that are not valid? assume this has to do with safeguarding against postal code that may not be in the system?

2) Why no client-side error-trapping for empty state and region fields? assume that these fields are not *always* required and it takes server-side logic to determine if they should be there or not?

thanks!
Comments
  • fc_adamfc_adam FoxyCart Team
    @freshjones,

    Great question. If a valid formatted postcode isn't entered, then the postcode field currently won't auto-validate, it will rely on the "Go" button being pressed. I can see what you're describing though and how it could be improved to catch customer entry errors like this. We'll look into this further and update as we're able to make any changes.
Sign In or Register to comment.