Backspace issues in version 1.9.1
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
Research direction
The payload names no file, class or test, so start by finding where the keyboard's delete-key handling sends backspace events to the input connection in the Kotlin Android sources. Reproduce it in a text field of a browser or a third-party app on Android 15, then check whether the deletion reaches the field. Done means backspace removes the mistyped character in those apps, with a reproduction that a maintainer can confirm.
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
Fennec F-Droid is my main use case. But we are talking many websites with input fields (and chrome browsers, android apps)
Affected Android/Custom ROM version
15 / Lineageos 22.2
Affected device model
NA
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Use backspace in certain apps or web pages and expect backspace to behave correctly on mistyping.
Expected behavior
Backspace correctly erasing character that has been mistyped.
Actual behavior
Backspace correctly erasing character instead it does nothing.
Screenshots/Screen recordings
No response
Additional information
No response
- 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 3/5 1-2 days Newbie friendliness 35/100
FossifyOrg/Keyboard#462 · 1 comment ·
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
utopia-rise/godot-jvm#1004 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ankidroid/Anki-Android#22408 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 Under an hour Newbie friendliness 72/100
afarber/OpenMapView#22 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nightscout/AndroidAPS#5245 ·
Maintainers usually reply within 1 day