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.

Sign up for GitHub

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

Jump to bottom

inputNumber with numeric prefix is not working as expected #15311

Closed
Anirudh16 opened this issue Apr 19, 2024 · 2 comments · Fixed by #15398
Closed

inputNumber with numeric prefix is not working as expected #15311

Anirudh16 opened this issue Apr 19, 2024 · 2 comments · Fixed by #15398
Labels
LTS-FIXED-16.9.9 Fixed in PrimeNG LTS 16.9.9 LTS-PORTABLE Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone
17.16.1

Comments

@Anirudh16
Copy link

Describe the bug

unable to enter 0 if prefix is given as 0

For Example:if we provide prefix as 0 and if we want to enter value as '10' then after 1 unable to enter 0

Please find the stackblitz link below for reference:
https://stackblitz.com/edit/1a8vuh?file=src%2Fapp%2Fdemo%2Finput-number-prefix-suffix-demo.ts

Environment

Windows 10

Reproducer

No response

Angular version

17.3.1

PrimeNG version

17.13.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.16.0

Browser(s)

Chrome

Steps to reproduce the behavior

1.Go to stackblitz link
2. In the primeng input try to enter 0,it wont allow

Expected behavior

it should allow 0 to be entered
@Anirudh16 Anirudh16 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 19, 2024
@Anirudh16 Anirudh16 changed the title inputNumber with numeric prefix is not working as expectedComponent: Title inputNumber with numeric prefix is not working as expected Apr 19, 2024
@cetincakiroglu cetincakiroglu added this to the 17.15.0 milestone Apr 19, 2024
@maruthumj
Copy link
Contributor

@Anirudh16 I don't think it's an issue for number 0 alone. the same issue occurs for any other prefix number.

@elian1780 elian1780 mentioned this issue Apr 20, 2024
Closed
@cetincakiroglu cetincakiroglu 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 26, 2024
@cetincakiroglu cetincakiroglu modified the milestones: 17.15.0, 17.16.0 Apr 26, 2024
@gercobrandwijk
Copy link

This one is probably also related? #13868

@nbrown-ScottLogic nbrown-ScottLogic mentioned this issue Apr 29, 2024
Merged
@cetincakiroglu cetincakiroglu modified the milestones: 17.16.0, 17.16.1 May 3, 2024
@mehmetcetin01140 mehmetcetin01140 added the LTS-FIXED-16.9.9 Fixed in PrimeNG LTS 16.9.9 label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
LTS-FIXED-16.9.9 Fixed in PrimeNG LTS 16.9.9 LTS-PORTABLE Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Milestone
17.16.1
Development

Successfully merging a pull request may close this issue.

Fixed inputNumber with numeric prefix is not working as expected nbrown-ScottLogic/primeng
5 participants
@gercobrandwijk @maruthumj @Anirudh16 @cetincakiroglu @mehmetcetin01140