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: Not working with azerty keyboard #5538

Closed
arlai-mk opened this issue Apr 5, 2024 · 1 comment
Closed

InputNumber: Not working with azerty keyboard #5538

arlai-mk opened this issue Apr 5, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@arlai-mk
Copy link

arlai-mk commented Apr 5, 2024

Describe the bug

Azerty keyboard specificities

French people mostly use Azerty keyboard instead of the most common qwerty one. It has a specificity that numbers (except on the pad) are used in combination with Shift key. It means that to type in "1", you need to type "Shift + 1".

The bug

It seems that the Shift key has some adverse effect on InputNumber component, meaning it will disable whatever is entered. Basically, it makes it impossible for azerty keyboard users to enter numbers in an InputNumber component, unless they:

  • use the numeric pad
  • use the "caps lock" then type in numbers

Thank you.

Reproducer

https://stackblitz.com/edit/primevue-create-vue-issue-template-tqwd1a

PrimeVue version

3.50.0

Vue version

3.x

Language

TypeScript

Build / Runtime

Vite

Browser(s)

No response

Steps to reproduce the behavior

You will need to install azerty keyboard (has been tested on Windows) and then use it, to see that numbers cannot be entered in the InputNumber component.
It has been tested on both Chrome and Firefox browsers, but is expected to be common to all browsers.

Expected behavior

It is expected that azerty keyboard users can also enter numbers in an InputNumber component.

@arlai-mk arlai-mk 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 5, 2024
@arlai-mk
Copy link
Author

arlai-mk commented Apr 8, 2024

My apologies, I realize that there was already an issue opened for this same bug: #5508
Closing this one now.

@arlai-mk arlai-mk closed this as completed Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

1 participant