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 was archived by the owner on Apr 12, 2024. It is now read-only.
A regression has occurred in Angular version 1.3.0-rc.1 where using ng-required on an input with type="number" results in incorrect behaviour on initialisation.
The issue is that regardless of what the ng-required expression returns, the input is marked as having an invalid number when it is empty due to being bound to a non-existent property.
I have reproduced this with a Plunkr, which shows output like so:
I was able to have a hacky workaround locally by creating a directive that would shift() the badInputChecker parser function from the start of the ngModelController.$parsers array, and push it onto the end instead. Thus it is likely related to the fact that the badInputChecker is added as the first parser function.