-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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: cannot shift + num key #6257
Labels
Type: Bug
Issue contains a defect related to a specific component.
Milestone
Comments
enzolry
added
the
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
label
Mar 29, 2024
enzolry
changed the title
InputNumber: cannot shift + numeric keys
InputNumber: cannot shift + num key
Mar 29, 2024
I think this is the same issue as #6237 |
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
Mar 29, 2024
melloware
added a commit
to melloware/primereact
that referenced
this issue
Mar 29, 2024
can you also go here and press SHIFT+NUM like you would so I can see what it does: https://w3c.github.io/uievents/tools/key-event-viewer.html |
Thanks! I think my PR will fix it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm using a 75% layout keyboard, so I don't have a numpad.
I upgraded to PrimeReact 10.5.3, and I realized much later that I could no longer use Shift+num key (above alphabetical keys) combination inside the input anymore.
Also, when I focus the input and click on a suggestion from browser, I get the following error
in inputnumber component at line 665
Reproducer
https://stackblitz.com/edit/vitejs-vite-olqmfh
PrimeReact version
10.5.3
React version
18.x
Language
TypeScript
Build / Runtime
Create React App (CRA)
Browser(s)
No response
Steps to reproduce the behavior
Expected behavior
No response
The text was updated successfully, but these errors were encountered: