Hi Sander, Thank you for the response. But in this case, even if the parent directive is not isolated, the '&' binding on the child directive is still choosing to parse from its own scope instead of from the parent's scope.
I was under the belief that the isolated scope's bindings '=','@','&' were ways to create a window to certain objects in the parent's scope. But then the '&' binding is somehow parsing it against the child's isolated scope, instead of parsing it against the parent scope and setting it into the child scope. Regards Parvathy On Tuesday, May 12, 2015 at 5:03:16 PM UTC+5:30, Sander Elias wrote: > > Hi Parvathy, > > An isolated scope is only usable from within the directive itself, and its > own template. If you want something like this, you can expose the > controller of the `parent-isolated-dir` with controllerAs, and use that. > If you really want to expose the scope to a directive's children, you must > create a new scope, in stead of an isolated scope > > 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.
