Thank you for that, I'm now convinced it is working as expected. Though I don't like the behavior, at least I have some workarounds if I encounter this again in the future.
On Saturday, September 27, 2014 1:02:08 AM UTC-5, Sander Elias wrote: > > Hi Zane, > > My first thought was that it expected behavior. But after some short > contemplating, and playing around with your plunk, getting confused. > It still counts as expected behavior. > Have a look at what I did with the plunk (before reading the rest of the > MSG! stop right here reading!, and check the plunk!) > > http://plnkr.co/edit/duHay8xzO6gZI08kWLh2?p=preview > > Even more confused? > It boils down to this. You can have only 1 (ONE!) scope per element. One > non-isolate scope that is. This is documented. > After the first digest cycle the correct scope is indeed assigned to your > div, and rereading the attribute, then reads the current scope. > > 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.
