You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
Calling NgModelController#$setViewValue(value, trigger) will call $$debounceViewValue()only if there is no ngModelOptions or ngModelOptions#updateOnDefault is true.
See here.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4). Demo
Clicking both buttons, I would expect both NgModelControllers to get updated.
The one with {updateOn: 'blur'} doesn't π
What is the expected behavior?
Calling NgModelController#$setViewValue(value, trigger) will also call $$debounceViewValue() if ngModelOptions#updateOn includes trigger.
What is the motivation / use case for changing the behavior?
To make it work as expected π
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
Only tried on 1.5.7, but it should affect many versions back.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
No π