From 5e140dbfd639e2e6d643266d5c6df4ac573d57a4 Mon Sep 17 00:00:00 2001 From: basarat Date: Wed, 3 Jul 2013 20:50:06 +1000 Subject: [PATCH] Update input.js --- src/ng/directive/input.js | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/ng/directive/input.js b/src/ng/directive/input.js index dfa52e85620e..54e2645699ec 100644 --- a/src/ng/directive/input.js +++ b/src/ng/directive/input.js @@ -843,6 +843,9 @@ 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 values would not get propogated to the parent. + * * * This example shows how to use `NgModelController` with a custom control to achieve * data-binding. Notice how different directives (`contenteditable`, `ng-model`, and `required`)