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?