Thanks for reply Sander, however the issue is slightly different than what
you propose. My secondary directive needs to be neutral in regard to
current scope and simple take what is available. I have however figured out
a workaround - it is to use element.isolateScope() method to get an access
to an existing isolated scope (if it exists). A better example of what I
mean could be found her http://plnkr.co/edit/DvjHfp?p=info
Sincerely,
Simon
On Thursday, February 27, 2014 11:05:17 PM UTC-5, Sander Elias wrote:
>
> Hi Sam,
>
> You probably need to use a new scope, in stead of an isolated scope on
> your outer directive.
> in your code, change scope: {} to scope : true
>
> This is not new or changed, only the bug that leaked isolated scopes into
> their childeren was fixed ;)
>
> 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/groups/opt_out.
