Hi Kingsly, ngChange is an directive, not an event-handler. The working is quite different. ngChange works by setting an scope.$watch, ngClick works by catching an event. This behaviour is as documented, so this is a feature, not a bug. I understand your confusion, it's an easily made mistake. If you want, you can create your own event handler using a (there is some irony here ;)) directive! What is it you are trying to accomplish? Perhaps I can help you finding an alternative solution.
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.
