It seems that whenever one of the values watched by ngOptions is changed, we might end up calling $setViewValue(). This seems incorrect if the changes can be a result of a change on the model side (as is the case in the above example).

@Narretz probably knows more.

The behavior is intentional: #7736 I can see how this can be confusing / unwanted, but it's an either-or situation and we've "fixed" this behavior, so we cannot go back. Why exactly is it a problem for your app that the model us updated @amiteshhh ?

@Narretz In our app we have a drop-down to select country. Based on country selection we display different information for that country. The information contains data for month drop-down(driven by country). By default we are initializing default month to show the default view. Additionally on change of month we fetch data for selected month.
Now user changes country to see information of other country and again we are fetching new set of data including months but at this moment ng-change handler of months automatically triggered by Angular(and this is the whole problem).
By maintaining the same reference of months array its not triggering the ng-change handler but this seems less obvious/awkward solution.

Following as this is also an issue for our team at present

It's my understanding that the purpose of ng-change is to know when the user changes the value. It's not supposed to fire simply when the model is changed programmatically.

I agree that the ng-model value should be updated in this particular case (as fixed in #7736), but I don't think the ng-change should be fired.

If this is an accurate understanding of the purpose of ng-change. could we get a fix for this?

@aaronpikkarainen AngularJS is in LTS mode, so we are only going to fix security bugs.