The ngModel
directive binds an input
,select
, textarea
(or custom form control) to a property on the scope using NgModelController, which is created and exposed by this directive.
ngModel
is responsible for:
input
, textarea
or select
require.ng-valid
, ng-invalid
, ng-dirty
, ng-pristine
) including animations.Note: ngModel
will try to bind to the property given by evaluating the expression on the current scope. If the property doesn't already exist on this scope, it will be created implicitly and added to the scope.
For best practices on using ngModel
, see:
For basic examples, how to use ngModel
, see:
The following CSS classes are added and removed on the associated input/select/textarea element depending on the validity of the model.
ng-valid
is set if the model is valid.ng-invalid
is set if the model is invalid.ng-pristine
is set if the model is pristine.ng-dirty
is set if the model is dirty.Keep in mind that ngAnimate can detect each of these classes when added and removed.
Animations within models are triggered when any of the associated CSS classes are added and removed on the input element which is attached to the model. These classes are: .ng-pristine
, .ng-dirty
, .ng-invalid
and .ng-valid
as well as any other validations that are performed on the model itself. The animations that are triggered within ngModel are similar to how they work in ngClass and animations can be hooked into using CSS transitions, keyframes as well as JS animations.
The following example shows a simple way to utilize CSS transitions to style an input element that has been rendered as invalid after it has been validated:
//be sure to include ngAnimate as a module to hook into more //advanced animations .my-input { transition:0.5s linear all; background: white; } .my-input.ng-invalid { background: red; color:white; }
<input> ... </input>
© 2010–2016 Google, Inc.
Licensed under the Creative Commons Attribution License 4.0.
https://code.angularjs.org/1.2.32/docs/api/ng/directive/ngModel