Entering invalid values in Horizon doesn't provide visual or textual feedback to user

[Duncan McGreggor]

When attempting to create a key pair with a space in the name, the page refreshes to /nova/access_and_security/keypairs/create/ with the key pair name in the form, but no message indicating that an illegal character has been entered.

[Duncan McGreggor (oubiwann)]

So this doesn't seem to be just the key pair field... seems that any field that gets an invalid/illegal input doesn't render any feedback to the user about this fact. I'll update the title of this bug... should probably check for duplicates or this, now that the issues seems to be more general.

[Andy Chong (andycjw)]

I believe this is fixed in https://review.openstack.org/4783
therefore, marked as duplicate

[Duncan McGreggor (oubiwann)]

Hrm, this shouldn't be a duplicate of that bug. That one specifically addresses the use of unicode and 500 errors.

The *fix* may be the same, but the bug is completely different.

This one specifically addresses a usability concern in the user interface: not presenting user feedback in forms where invalid entry has occurred. Users need to see what has gone wrong, when something does go wrong.

I'm going to unmark this as a duplicate, but what I will do is assign the bug to myself and check that the fix for bug #898808 does indeed address the issue. I'll update the ticket with my findings, and close it out as "Fix Released" if the patch you mentioned does address it.

[Duncan McGreggor (oubiwann)]

Oops, I meant "Fix Committed" (if the patch you mentioned addresses the usability concerns).

[Gabriel Hurley (gabriel-hurley)]

This has been fixed for quite some time. Individual field errors have displayed for months, whereas non-field form errors were recently fixed. I just verified this now, though, and the keypairs name field definitely displays errors appropriately. If yo ucan find specific cases where this is not true please open new bugs. Thanks!