p-inputnumber infinite loop when using buttons #9888
Labels
LTS-FIXED-9.2.4
Fixed in PrimeNG LTS 9.2.4
LTS-FIXED-10.0.9
Fixed in PrimeNG LTS 10.0.9
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
Milestone
If you have a PrimeNG PRO Support subscription please post your issue at;
https://pro.primefaces.org
where our team will respond within 4 business hours.
If you do not have a PrimeNG PRO Support subscription, fill-in the report below. Please note that
your issue will be added to the waiting list of community issues and will be reviewed on a first-come first-serve basis, as a result, the support team is unable to guarantee a specific schedule on when it will be reviewed. Thank you for your understanding.
Current Queue Time for Review
Without PRO Support: ~8-12 weeks.
With PRO Support: 1 hour
I'm submitting a ... (check one with "x")
Plunkr Case (Bug Reports)
Please demonstrate your case at stackblitz by using the issue template below. Issues without a test case have much less possibility to be reviewd in detail and assisted.
https://stackblitz.com/github/primefaces/primeng-issue-template
Current behavior
Given an inputnumber with buttons, if i attach a method to the onInput (same thing with ngModelChange) event and in that
method i change the disable state of the inputnumber, we have the method repeat (method of inputnumber.ts sourcecode) call itself infinitely.
seems like the mousedown event get trapped in the method.
From inputnumber.ts, this method is the culprit.
Expected behavior
no infinite loops.
Minimal reproduction of the problem with instructions
https://stackblitz.com/edit/angular-ivy-ocoqgf?file=src/app/hello.component.ts
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Angular version: 11.2
PrimeNG version: 11.2
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [all | TypeScript X.X | ES6/7 | ES5]
Node (for AoT issues):
node --version
=The text was updated successfully, but these errors were encountered: