Hi AngularN00b,
An isolated scope is isolated to the element itself! This means it’s usable to the directive itself, and in the template used by that directive. It is not exposed to children of the directive’s element. have a look at this: http://jsbin.com/volohuwi/1/edit?html,js,output Oh, this leaking into children was a bug that was repaired somewhere very early in the 1.2 version. If you need this kind of behavior, you don’t need an isolate scope, but a new scope (sometimes called private scope) created by scope : true in your directive Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
