Description of problem:

Low priority!

It seems that the "Save User" button gets disabled during one - and only one circumstance - when the entered passwords don't match.  Otherwise there are plenty of other methods by which the user can enter incomplete data and the Save User button is enabled.  Wondering but if there should be some uniformity.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. +New User; observe state of "Save User" button.
2. Enter Username; observe state of "Save User" button - hit save user
3. Enter "redhat" in password field; observe state of "Save User" button.
4. Enter "fibble" in confirm field; observe state of "Save User" button.
5. Enter "redhat" in confirm field; ; observe state of "Save User" button - hit save user
6. Enter "username" in Email address field; observe state of "Save User" button - hit save.
  
Actual results:

During most of these steps, user creation will be rejected, which is ostensibly correct. However, when password fields don't match, the "Save user" button is disabled.  
Expected results:

It seems to me that we should either
(a) disable Save User button anytime we have incomplete data, or
(b) modify the apparently one-off behavior that disables the "Save User" button when passwords are incorrect.  Of course, this would require error-checking to be enabled on password submit (don't create a user when Password != Confirm)


Additional info:
In all, very low priority, but somewhat odd user experience