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

p-InputNumber : minFraction digit not working as expected #13833

Closed
KevinHetzelGFL opened this issue Oct 9, 2023 · 1 comment
Closed

p-InputNumber : minFraction digit not working as expected #13833

KevinHetzelGFL opened this issue Oct 9, 2023 · 1 comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@KevinHetzelGFL
Copy link

Describe the bug

inside p-inputnumber, the displayed value and the stored value of the component are different if you use minFractionDigits. I configured my inputNumber with minFractionDigits and maxFractionDigits 2 to get always a number with 2 digits. It is working on the UI, but the stored value somethimes has no digits.
This occurs when the typed number has no digits like "1" or if you type 0 as digit.

Environment

Angular 16 app. Can also be reproduced on the demo page of primeng

Reproducer

https://codesandbox.io/p/sandbox/primeng-input-number-numerals-demo-forked-n9ndg8

Angular version

16.2.2

PrimeNG version

16.3.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.14.0

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

Input: 6
Displayed value: 6.00
stored value: 6
expected 6.00

@KevinHetzelGFL KevinHetzelGFL added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Oct 9, 2023
Copy link

This issue has been automatically marked as stale due to a lack of activity. If this issue is still relevant to you, please leave a comment so we can keep it open. We apologize for not being able to prioritize it sooner. If you have any new information or questions, please share them in your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response 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

2 participants