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.
What is the current behavior?
When you have a form that is shown using ngIf and contain an <input type="email" ng-model="someModel" required>, ngAnimate classes are not added when the ngIf statement becomes truthy.
Hey!
What is the current behavior?
When you have a form that is shown using
ngIfand contain an<input type="email" ng-model="someModel" required>, ngAnimate classes are not added when thengIfstatement becomes truthy.Steps to reproduce
Link to demo
ngIfand contains an<input type="email" ng-model="someModel" required>ngIfstatement truthyWhat is the expected behavior?
ngAnimate classes should be added when
ngIfstatement becomes truthy.What is the motivation / use case for changing the behavior?
Consistent behavior
Affected:
This occured when I tested with Chrome and Firefox on Linux, Safari on OSX, and Chrome / IE on Win7, both angular 1.5.x stable and snapshot.
Other information
It works as expected if:
type="email"is changed to something elserequiredis removedngShow / ngHideis used instead ofngIf