From a3fb0f79fe7067d2fd45b9d1833a38aee06b5b1a Mon Sep 17 00:00:00 2001 From: Craig Tataryn Date: Sat, 16 Apr 2011 14:20:30 -0500 Subject: [PATCH] Added a bit more documentation to ng:autobind to explain some of the semantics --- src/Angular.js | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/Angular.js b/src/Angular.js index 1762c11d2495..21c03ff5a072 100644 --- a/src/Angular.js +++ b/src/Angular.js @@ -895,7 +895,13 @@ function encodeUriQuery(val, pctEncodeSpaces) { </html> * * - * The `ng:autobind` attribute without any value tells angular to compile and manage the whole HTML + * Essentially, Angular does not want to be over-zealous and assume the entire HTML document should be + * processed based soley on the fact you have included the angular.js script. It will only + * process the entire document if you have specify ng:autobind attribute or #autobind anchor. There + * might be a case where you want Angular to only process a certain sub-section of your template. + * You'll determine which sub-sections to process using one of the following techniques. + * + * As stated, the `ng:autobind` attribute without any value tells angular to compile and manage the whole HTML * document. The compilation occurs as soon as the document is ready for DOM manipulation. Note that * you don't need to explicitly add an `onLoad` event handler; auto bind mode takes care of all the * work for you.