Number keypad not allowing field completion
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
The payload names no source files. Start by reproducing on Android: open a numeric field with a three-digit limit, such as a CVV, and see where the number keypad input stops at two digits. Then find the keypad's input or max-length handling in the Kotlin code. Done means the field accepts three digits on the number keypad, and the change works with the stock keyboard comparison also noted in the issue.
Written by the indexing model from the issue text.
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.9.1
Affected Android/Custom ROM version
GrapheneOS
Affected device model
Pixel 9 Pro XL
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
- Check out in The Home Depot app and enter information for a credit card at checkout.
Expected behavior
Three digits to be entered and continue.
Actual behavior
For the CVV, the number pad come up and instead allowing three digits to be input, only two is allowed.
Screenshots/Screen recordings
No response
Additional information
Switching to the stock GrapheneOS keyboard allow for completion.
- Dominant language
- Kotlin
- Stars
- 678
- Forks
- 84
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- No 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 FossifyOrg/Keyboard
-
Error of the Ukrainian keyboard layoutPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
FossifyOrg/Keyboard#487 · 1 comment ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Keyboard#484 ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 18/100
FossifyOrg/Keyboard#450 ·
Maintainers usually reply within 5 days
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
FossifyOrg/Keyboard#447 ·
Maintainers usually reply within 5 days
-
feature request needs triage
Difficulty 5/5 Over a week Newbie friendliness 8/100
FossifyOrg/Keyboard#440 ·
Maintainers usually reply within 5 days
All issues in FossifyOrg/Keyboard
Similar issues
-
bugbane/qf good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
osservatorionessuno/bugbane#173 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Bayern feature:Application ready web
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
digitalfabrik/entitlementcard#3176 ·
Maintainers usually reply within 7 days
-
bug need-device
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
ramesh130/superplayer#495 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
maxrave-dev/SimpMusic#2649 ·
Maintainers usually reply within 2 days