From 295043d32e27fdea26cfe3f8a9a7d47c5d292f5a Mon Sep 17 00:00:00 2001 From: Martin Staffa Date: Wed, 22 Feb 2017 20:07:28 +0100 Subject: [PATCH] docs($compile): clarify to which element scope isolation applies Closes #13556 --- src/ng/compile.js | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/ng/compile.js b/src/ng/compile.js index 028901f06..d5e237c6a 100644 --- a/src/ng/compile.js +++ b/src/ng/compile.js @@ -277,10 +277,12 @@ * the directive's element. If multiple directives on the same element request a new scope, * only one new scope is created. * - * * **`{...}` (an object hash):** A new "isolate" scope is created for the directive's element. The - * 'isolate' scope differs from normal scope in that it does not prototypically inherit from its parent - * scope. This is useful when creating reusable components, which should not accidentally read or modify - * data in the parent scope. + * * **`{...}` (an object hash):** A new "isolate" scope is created for the directive's template. + * The 'isolate' scope differs from normal scope in that it does not prototypically + * inherit from its parent scope. This is useful when creating reusable components, which should not + * accidentally read or modify data in the parent scope. Note that an isolate scope + * directive without a `template` or `templateUrl` will not apply the isolate scope + * to its children elements. * * The 'isolate' scope object hash defines a set of local scope properties derived from attributes on the * directive's element. These local properties are useful for aliasing values for templates. The keys in