From 861e0c75bd60706d1fd4076d6a7b205c18bb63c9 Mon Sep 17 00:00:00 2001
From: basarat
Date: Wed, 3 Jul 2013 20:50:06 +1000
Subject: docs(input): ng-model doesn't work well with isolated scope directive

Closes #3123
---
 src/ng/directive/input.js | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'src/ng')

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`)
-- 
cgit v1.2.3