$viewChangeListeners not called with <input type="radio">

[lovasoa]

Bug report

How to reproduce

1. Open the following jsfiddle: http://jsfiddle.net/ADukg/10031
2. Click the button
3. Tick the second radio checkbox
4. Tick the first radio checkbox

What is the current behavior?

An alert appears ONLY after step 3.

What is the expected behavior?

An alert should appear after step 3 and 4.
The functions specified in $viewChangeListeners should be called every time the view value changes, as stated in the documentation

Which versions of AngularJS, and which browser / OS are affected by this issue?

The fiddle demonstrates the bug with the latest snapshot of angular.
Tested in both firefox and chrome.

Other information (e.g. stacktraces, related issues, suggestions how to fix)

The issue was reported here on stackoverflow: http://stackoverflow.com/questions/34703156/only-last-radio-button-triggers-viewchangelistener

[edenferreira]

I see angular 1.0.1 on your jsFiddle. I've updated to 1.6.1 and appears to work http://jsfiddle.net/ADukg/10030/

[lovasoa]

@edenferreira I updated the fiddle. The bug is still present. In older versions of angular, step 4 worked and step 3 didn't, in newer versions, it's the opposite, but the bug is always present.

[gkalpak]

@lovasoa, the problem is that controls are registered on their parent form by their name. Having the same name on one than one controls, the last one registered (usually the last to appear in DOM) overwrites all the others. This is what is happening here. Note that (unlike "traditional" HTML forms), readio buttons do not need the same name on AngularJS forms. You can either give them unique names or omit the name property altogether and let AngularJS assign unique names automatically.

Since each control has its own instance of NgModeController, you need to hook into each one's $viewValueListeners. Alternatively, you can use the ngChange directive, which does exctly that.

Closing since everything works as expected, but feel free to continue the discussion below.

[lovasoa]

This is still at least very confusing. The documentation states that $viewValueListeners is an Array of functions to execute whenever the view value has changed.. Here, the view value changes, and the function isn't called.

The documentation also states that

This can be used in place of additional $watches against the model value.

Here, the result is clearly different from what we would get by placing a $watch on the model value.

[gkalpak]

Actually, you are right: Something is wrong. Even if the $viewChangeListener is attached to the last radio button, it does not fire when the value changes (by selecting the other radio button).