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: format error after the decimal point when Locale set de-DE. #5745

Closed
vnedevaa opened this issue Jan 11, 2024 · 6 comments · Fixed by #5734
Closed

InputNumber: format error after the decimal point when Locale set de-DE. #5745

vnedevaa opened this issue Jan 11, 2024 · 6 comments · Fixed by #5734
Assignees
Labels
Type: Bug Issue contains a defect related to a specific component.
Milestone

Comments

@vnedevaa
Copy link

Describe the bug

The issue involves the de-DE locale, where typing decimals starting with '0' produces unexpected results. For example, entering '0,01' results in '0,10' instead of the expected '0,01'.

Reproducer

No response

PrimeReact version

10.3.1

React version

18.x

Language

TypeScript

Build / Runtime

Create React App (CRA)

Browser(s)

No response

Steps to reproduce the behavior

  1. Type '0' after the decimal point.
  2. Then type '1'.

Actual result: '0,10'

Expected behavior

Expected result: '0,01'

@vnedevaa vnedevaa added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 11, 2024
@melloware
Copy link
Member

cc @kl-nevermore

@melloware 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 Jan 11, 2024
@melloware melloware modified the milestone: 10.4.0 Jan 11, 2024
@kl-nevermore
Copy link
Contributor

kl-nevermore commented Jan 11, 2024

@vnedevaa
Can you check that is the same as #5728(since10.1.0, fixed by #5734)

master branch code

20240111220803_rec_

@vnedevaa
Copy link
Author

@kl-nevermore Yes, it is the same

@kl-nevermore
Copy link
Contributor

@vnedevaa
If possible, you can test again on the master branch

@melloware
Copy link
Member

I linked that PR here as I thought it was the same issue.

@vnedevaa
Copy link
Author

@vnedevaa If possible, you can test again on the master branch

Hello, sorry for the delayed reply. I have tested it on the master branch, and it looks okay.

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

Successfully merging a pull request may close this issue.

3 participants