I believe the transcluded content is not in the isolate scope. Do you absolutely require isolate scope in your app?
On Thursday, January 16, 2014 7:34:47 AM UTC-7, Olivier Clément wrote: > > Hi all > > I've updated my app to 1.2.5 when it was released, and found there was a > few things that broke regarding custom directives and scopes > I've been looking at the changelogs and all and couldn't see anything that > would affect this, but it definitely seems like a change on the angular > side of things. > > I'd like to see if there's any documentation on this and the what how and > why of it all. > > Here's a Plunk that describe the kind of issue I'm experiencing: > http://plnkr.co/edit/ze6TyfstXnlLbOLq0xe3 > > Basically, before the upgrade (I think I was still on 1.2.0rc3), I could > do this: > > <custom-dir ng-click='definedOnDirectivesScope()'></custom-dir> > > The method would be defined on the directive's isolated scope and all > would be fine > > Now it's looking for this method on the parent's scope, unless I define > the ng-click *inside* the directive's template. That goes for > ng-click/ng-class/etc. > > Any input is appreciated > > Thanks > -- 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.
