Thanks Sander... I apparently missed the fact that directive's scope only applies to the directive's templated and not to the children of the directive.
Now I am trying to get two way binding to work in my directive's template - http://jsbin.com/volohuwi/3/edit?html,js,output Can you explain why myParentProperty is not being bound in my directive's template? On Thursday, March 20, 2014 12:42:49 AM UTC-4, Sander Elias wrote: > > 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.
