use ngModelController $viewValue and not $modelValue because the isActive state (and so active class of buttons) should be synchronized with viewValue.
For example, if a ngModelOptions is used with debouncing, $modelValue still equals the previous value on $render execution
use ngModelController
$viewValue
and not$modelValue
because theisActive
state (and so active class of buttons) should be synchronized with viewValue.For example, if a ngModelOptions is used with debouncing,
$modelValue
still equals the previous value on$render
executionThat's a fix for #2164. Here is a fiddle using patch : https://jsfiddle.net/elkami/pkj3x9xr/
Thanks for review