Hi Nadia, Your issue lies into the use of ngIf. I can't explain it exactly, but it has to do with the fact that ngIf recreates the element using their compiled state <http://docs.angularjs.org/api/ng/directive/ngIf>. Combined with the transclusion and the isolated scope I lost track of what happens. I'm note sure if this is a bug, or by design. You might file a bug on git on this issue, and find out what the core team thinks of this.
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.
