Hi Dave, No, not a security issue. When you change some value's using the debuger, you are changing the value in the DOM. That value is an result of angular, not the actual value. Angular does NOT read those DOM values ever. The only directive that monitors a value is ngModel, and then you need at least one $digest cycle to get it back into angular. So, setting a angular value in a way you like to do is put the wanted value inside the dom-elements value propertie, and trigger an $apply inside your app, then angular will pick up the value, and send it over. Does that explain it enough for you?
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.
