Closed Zodiark1020 closed 1 day ago
Hi,
Could you please share a stackblitz example so we can identify the issue clearly?
Hi, sure. It's a test with ngModel; prints trigger count and what I deem to be valid trigger count: inputNumber test
Any news about this issue?
Describe the bug
When using p-inputNumber component with updateOn 'blur' strategy, the model is updated on blur even when no changes were made. This causes many unwanted notifications to the form and potentially to other controls.
My use case is in a reactive form, though this behaviour also happens with ngModel due to the else if in this method:![img](https://github.com/primefaces/primeng/assets/42294130/d3cd1087-26ae-4c8a-9aa3-1f00ff45f15e)
Environment
Angular 17 PrimeNG 17.17.0
Reproducer
No response
Angular version
17.3.x
PrimeNG version
17.17.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.x
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
I expect what already happens on updateOn 'change', i.e., when the value hasn't changed there is no need to call onModelChange