This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
ngAnimate messing with validation classes #12266
Comments
I am pretty sure there is a duplicate issue, but I can't find it 😞 |
Looks like a dupe of #12007 |
Yup, that's the one ! |
Can confirm that it works fine with a snapshot of 1.4.4. Thank you! |
netman92
pushed a commit
to netman92/angular.js
that referenced
this issue
Aug 8, 2015
…d when cancelled Instead of merging existing animation option to new animation options we can merge in reverse and utilize old animation runner. Closes angular#12266 Closes angular#12007
ggershoni
pushed a commit
to ggershoni/angular.js
that referenced
this issue
Sep 29, 2015
…d when cancelled Instead of merging existing animation option to new animation options we can merge in reverse and utilize old animation runner. Closes angular#12266 Closes angular#12007
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since 1.4.0, ngAnimate has been messing with the way ng-valid/ng-invalid classes are being applied. Here's a plunker with an example (forked from the official email example): http://plnkr.co/edit/THMRi4lrFoVUMOFsmeli?p=preview
To reproduce, try entering any random value whose length is divisble by 3 (e.g. "123"). Note that the input and the form have the
ng-valid
class, in addition tong-invalid-email
, even though the value isn't a valid email. The correct behavior is for them to both beng-invalid
.The problem gets solved if
ngAnimate
gets commented out from the dependencies.The text was updated successfully, but these errors were encountered: