You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 29, 2019. It is now read-only.
When a bad value is entered in the timepicker, the input displays as invalid (that is, the class has-error is applied to the parent <td>, with which it can be styled as an error), but the class ng-invalid isn't applied to the input element itself (it will remain as ng-valid).
There may be other problems with this, but in my use case this conflicts with ngAria. ngAria will add the attribute aria-invalid to the element and set it to true or false based on the presence of the ng-valid or ng-invalid classes.
Reproduce the issue:
View the Timepicker on the demo page
Enter the value 'z' into the Hours input in the Start Time
Inspect this input and notice the presence of ng-valid
Version of Angular, UIBS, and Bootstrap:
Angular: 1.5.2
UIBS: 2.0.2
Bootstrap: 3.3.1
The text was updated successfully, but these errors were encountered:
Bug description:
When a bad value is entered in the timepicker, the input displays as invalid (that is, the class
has-error
is applied to the parent<td>
, with which it can be styled as an error), but the classng-invalid
isn't applied to the input element itself (it will remain asng-valid
).There may be other problems with this, but in my use case this conflicts with ngAria. ngAria will add the attribute
aria-invalid
to the element and set it totrue
orfalse
based on the presence of theng-valid
orng-invalid
classes.Reproduce the issue:
ng-valid
Version of Angular, UIBS, and Bootstrap:
Angular: 1.5.2
UIBS: 2.0.2
Bootstrap: 3.3.1
The text was updated successfully, but these errors were encountered: