diff options
| author | basarat | 2013-07-03 20:50:06 +1000 | 
|---|---|---|
| committer | Pete Bacon Darwin | 2013-07-04 00:35:34 +0100 | 
| commit | 861e0c75bd60706d1fd4076d6a7b205c18bb63c9 (patch) | |
| tree | 0ef088ce4e06627f0eb673da0cab4ffe9113dbea /src/ng/directive/input.js | |
| parent | 0e9e0af9755232ef3ac4858379cc155444a9ba5c (diff) | |
| download | angular.js-861e0c75bd60706d1fd4076d6a7b205c18bb63c9.tar.bz2 | |
docs(input): ng-model doesn't work well with isolated scope directive
Closes #3123
Diffstat (limited to 'src/ng/directive/input.js')
| -rw-r--r-- | src/ng/directive/input.js | 4 | 
1 files changed, 4 insertions, 0 deletions
| diff --git a/src/ng/directive/input.js b/src/ng/directive/input.js index dfa52e85..a5fc56c8 100644 --- a/src/ng/directive/input.js +++ b/src/ng/directive/input.js @@ -843,6 +843,10 @@ var VALID_CLASS = 'ng-valid',   * specifically does not contain any logic which deals with DOM rendering or listening to   * DOM events. The `NgModelController` is meant to be extended by other directives where, the   * directive provides DOM manipulation and the `NgModelController` provides the data-binding. + * Note that you cannot use `NgModelController` in a directive with an isolated scope, + * as, in that case, the `ng-model` value gets put into the isolated scope and does not get + * propogated to the parent scope. + *    *   * This example shows how to use `NgModelController` with a custom control to achieve   * data-binding. Notice how different directives (`contenteditable`, `ng-model`, and `required`) | 
