activation-key: red border doesn't appears on updating content-host limit with invalid value
|Assigned To:||Walden Raines|
|Target version:||Katello - Team Tom - backlog|
|Velocity based estimate||-|
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1131204
Description of problem:
Found a failure in automation where we are updating the content-host-limit of an existing activation-key with some invalid value (say with some string), and UI doesn't highlight the input box with red border and save button remains disabled.
Please note that this happens only while editing the activation-key. When we use invalid limit while creating activation-key, the red border appears. So the behaviour should be consistent with create activation-key.
Version-Release number of selected component (if applicable):
sat6 GA snap5
Steps to Reproduce:
1. create a activation-key with default content-host-limit
2. update the limit with either string or -ve value
UI doesn't highlight the input box with red border, when we update content-host-limit with some invalid value.
UI should highlight the input box with red border while updating the limit with some invalid value
#4 Updated by Walden Raines over 2 years ago
- Status changed from Assigned to New
I looked into this some and I believe that rewriting our error messages using ngMessages (https://docs.angularjs.org/api/ngMessages/directive/ngMessages) is the way to go. ngMessages is available in Angular 1.3, which is currently in beta, so I am moving this back to "new" status until Angular 1.3 is released.