Does the same problem with ngModel (setting the value on the wrong scope) happen to isolate scope bindings? I was under the impression it doesn't, but I have an isolate scope directive that sets the new value on its parent scope rather than the scope it read the property from (its grandparent scope). I have described the issue in more detail here: http://stackoverflow.com/questions/43945273/ngif-scope-defining-value-on-itself
-- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" 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 https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
