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
If onValueChange handler of InputNumber disables the component, then event generated by clicking on the component's button keeps reoccurring infinitely.
melloware
added
Type: Bug
Issue contains a defect related to a specific component.
and removed
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
labels
Nov 6, 2023
Describe the bug
If
![ezgif-4-c2be353dd6](https://private-user-images.githubusercontent.com/48034657/280552612-6f720141-fc2e-4d7f-9338-9a1fb331fa74.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMzNDgyNDcsIm5iZiI6MTcyMzM0Nzk0NywicGF0aCI6Ii80ODAzNDY1Ny8yODA1NTI2MTItNmY3MjAxNDEtZmMyZS00ZDdmLTkzMzgtOWExZmIzMzFmYTc0LmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODExVDAzNDU0N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM0OGM1MzA2NGE2Nzk5YWJjYmQ4ODM4NWQyMWNmMDFiNWYxNzQ0ZDA4MTE5YzVkYjA5ZTlkYjFiYWZkMDA0NGQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.5w0In3zIoGWGiBIirM33ihJOCXnp0hX7KXcLDJKN9h4)
onValueChange
handler of InputNumber disables the component, then event generated by clicking on the component's button keeps reoccurring infinitely.Same bug was reported on primeng primefaces/primeng#9888
Reproducer
https://codesandbox.io/s/primereact-demo-forked-lvwxvl
PrimeReact version
10.0.x
React version
17.x
Language
ES6
Build / Runtime
Create React App (CRA)
Browser(s)
Chrome, Firefox
Steps to reproduce the behavior
Click on
+
or-
button of the InputNumber component.Expected behavior
Single button click should generate a single value change event.
The text was updated successfully, but these errors were encountered: