Field validation in forms should be done on the client side

[Stuart Metcalfe]

Based on the design team's guidelines, the form fields in the sso service should be validated on the client side using javascript wherever possible. This doesn't make sense for the login form itself but should be used for account management and account creation/password reminder where passwords are set. We shouldn't live-check the existence of email addresses in the system but we can check for email address validity.

This shouldn't replace server side validation, obviously!

[Michael Nelson (michael.nelson)]

Just a note that this can be done *really* easily without any javascript for most modern browsers. Here's a branch for SCA which adds client side validation (with a 40sec video demo'ing it):

https://code.launchpad.net/~michael.nelson/software-center-agent/860507-basic-client-validation/+merge/77188

[Daniel Manrique (roadmr)]

I think they are: I tried a few invalid e-mail addresses and they pop up an "invalid" message which seems to be generated clientside, using newer browsers' validation for<input type="email">. Also the password is checked for length, strength and matching on the client. This is the case both on the new account form, and the existing account editing forms.

I'll close this report now, but if any of the existing behaviors needs tweaking per the design team's guidelines, it can be reopened.