Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Commit 0fa5a37

Browse files
jugglinmikeNarretz
authored andcommitted
docs(ngNonBindable): document effect on the element's directives
The phrase "contents of the current DOM element" may be interpreted either as inclusive of the DOM element's attributes or as exclusive of the attributes. This situation concerns markup such as: <div ng-non-bindable ng-controller="MyController"></div> In practice, AngularJS does not compile or bind attribute values for elements which specify the `ng-non-bindable` directive. Extend the documentation to definitely describe this behavior. Closes #16338
1 parent 07e4751 commit 0fa5a37

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

src/ng/directive/ngNonBindable.js

+4-3
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,10 @@
99
*
1010
* @description
1111
* The `ngNonBindable` directive tells AngularJS not to compile or bind the contents of the current
12-
* DOM element. This is useful if the element contains what appears to be AngularJS directives and
13-
* bindings but which should be ignored by AngularJS. This could be the case if you have a site that
14-
* displays snippets of code, for instance.
12+
* DOM element, including directives on the element itself that have a lower priority than
13+
* `ngNonBindable`. This is useful if the element contains what appears to be AngularJS directives
14+
* and bindings but which should be ignored by AngularJS. This could be the case if you have a site
15+
* that displays snippets of code, for instance.
1516
*
1617
* @example
1718
* In this example there are two locations where a simple interpolation binding (`{{}}`) is present,

0 commit comments

Comments
 (0)