Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InputNumber: The InputNumber is not working properly in the new version 3.51.0 #5602

Closed
RezaPourshariati opened this issue Apr 16, 2024 · 4 comments
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@RezaPourshariati
Copy link

Describe the bug

In the current version of PrimeVue (3.51.0), the component InputNumber is not working correctly and there might be a bug or issue with this component. on incrementing and decrementing the button, the value doesn't change and stays in the same state as before!
I have tested it with the latest version of Vue (3.4.22), Vite(5.2.9), and PrimeVue(3.51.0)

"dependencies": { "primeicons": "^7.0.0", "primevue": "^3.51.0", "vue": "^3.4.22" },

"devDependencies": { "@vitejs/plugin-vue": "^5.0.4", "vite": "^5.2.9" }

Reproducer

https://stackblitz.com/edit/vitejs-vite-b4chsj?file=package.json

PrimeVue version

3.51.0

Vue version

3.x

Language

ES6

Build / Runtime

Vite

Browser(s)

No response

Steps to reproduce the behavior

  1. Go to the Stackblitz link that I shared.
  2. Click on the incrementing and decrementing buttons to see the behavior.

Expected behavior

The value of the InputNumber component should change on clicking buttons of the InputNumber (to increment or decrement value). but the value remains unchanged from its initial state!

@RezaPourshariati RezaPourshariati added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Apr 16, 2024
@forNoor
Copy link

forNoor commented Apr 17, 2024

Same Problem.
thanks to solve it immediately

@RezaPourshariati RezaPourshariati changed the title InputNumber: the InputNumber is not working properly in the new version 3.51.0 InputNumber: The InputNumber is not working properly in the new version 3.51.0 Apr 17, 2024
@VapoFred78
Copy link

VapoFred78 commented Apr 23, 2024

Yes, I can confirm that. This problem arises when we use a keyboard that doesn't have a numeric keypad, as is often the case on laptops, for example. If you have to press the SHIFT key to get a number, you're screwed. If you use the numbers directly on a numeric keypad, no problem.

@KTelineSama
Copy link

KTelineSama commented Apr 23, 2024

Same issue here, even got some "undefined " when I delete the number with CTRL+Del

@tugcekucukoglu tugcekucukoglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Apr 25, 2024
@tugcekucukoglu tugcekucukoglu added this to the 3.52.0 milestone Apr 25, 2024
@tugcekucukoglu tugcekucukoglu self-assigned this Apr 25, 2024
@MarkoMarinovic
Copy link

MarkoMarinovic commented Jun 5, 2024

I am still having the same issue in version 3.52.0. @tugcekucukoglu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

6 participants