Thanks for clarifying that Sander. I know that using 'new' for the scope parameter of the directive will bind the scope the way I want it, but it will also bring all the baggage from the parent scope that I don't want. Wish there was something like a "blank" option that worked like new but didn't inherit from the parent.
As to your plunker, it's not working for me. If you look at the output, inner.val is not being shown, suggesting to me that the isolate scope is not being bound to the view. Thanks so much again, this is all very interesting. On Thursday, 1 May 2014 05:06:51 UTC+1, Sander Elias wrote: > > Matthew, > > As you can see, it works fine with 1.0.8. The inner controller scope is >> bound to the inner view and does not have the inherited attributes. But go >> into index.html and change the angular version to 1.2.16 and it stops >> working. Now the view is bound to the *outer* scope for some reason! >> Very strange... >> > > This was a bug that got fixed early on in 1.2 somewhere. The older > versions had a bug that leaked the isolated scope into their children. If > you need that, you don't need an isolate scope, but a new scope. > An isolated scope is just that, isolated to the directive that creates it. > > > 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.
