Currently client-side validation is used only for few resources. However in same cases the validation is incorrect and valid values are being rejected (see BZ1018800 or BZ1019303), which is even worse than no validation at all. Also afaik client-side validation is completely separated from the one on server. This should be addressed in future versions of console with the possibility of re-using server side validation logic/rules in client.
Postponed to EAP 6.3
In agreement with Catherine we've decided that UX issues will be tracked separately.
Issue moved under the UX component. Also moved to 6.4 as this issue is still valid for 6.3. Use ack flags to decide whether we want to go through with it or not.
Will be bundled into UX messaging and validation work to be addressed in EAP 7.