InputNumber: Caret jump in decimal fields on Android
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react
- Domain
- frontend
Research direction
Start with the InputNumber component and reproduce the issue at primereact.org/inputnumber using an Android device or Chrome's mobile emulation. Exercise the Min-Max Fraction Digits field by deleting the integer digits and entering two new digits. Done means deletion updates the value correctly and both new digits remain in the integer part, matching desktop and iOS behavior.
Written by the indexing model from the issue text.
Description
Describe the bug
The issue occurs in the InputNumber component with Min-Max Fraction Digits (decimal) on Android Devices. If a user deletes the digits in the integer part (before the separator) and then types two new digits.
The first digit is placed in the integer part, but the second digit is automatically placed in the fractional part (caret jump). The field value does not update correctly upon deletion as on iOS and desktop browsers.
Reproducer
No response
System Information
Product name: Xiaomi Redmi 8A
OS: Android 10
Primereact: 10.9.7
Browser: Google Chrome 144.0.7559.109
Steps to reproduce the behavior
- Go to www.primereact.org/inputnumber
- Click on input number with Min-Max Fraction Digits in the page.
- Delete the numbers located before the separator.
- Enter two numbers.
Expected behavior
The field value is updated correctly upon deletion. The second digit is placed in the integer part. Behavior is as expected on desktop browsers and iOS.
- Dominant language
- CSS
- Stars
- 8.3k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from primefaces/primereact
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
primefaces/primereact#8552 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
primefaces/primereact#8550 ·
-
Row checkbox selection tick is invisible in Landing Page Theme sectionPossibly taken @Prakash1185 claimed this 173 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
primefaces/primereact#8545 ·
-
Dependency conflict between jspdf v4 and jspdf-autotable during npm installPossibly taken @Kamran92 claimed this 187 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
primefaces/primereact#8537 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
primefaces/primereact#8551 ·
All issues in primefaces/primereact
Similar issues
-
[BUG]: Shared links drop the configured basePath on GitHub PagesPossibly taken @anshulchikhale30-p claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Leonxlnx/taste-skill#216 ·
Maintainers usually reply within 1 day
-
area: ui Bug Payload OSS
Difficulty 1/5 Under an hour Newbie friendliness 88/100
payloadcms/payload#19839 ·
Maintainers usually reply within 1 day
-
BoxShadow.lerp returns the wrong blur style at t = 0 or t = 1Possibly taken @ArtemChikolaev claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day