Calculator: The C (Clear) button in the unit converter only deletes one character instead of clearing the input
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 58/100
Research direction
Start by reading the unit converter FAQ and locating the C button label and its accessibility or explanatory text; the issue does not name source files or tests. The reported behavior is intentional: C deletes one character and a long press resets all fields. Done means the label or wording no longer implies that a tap clears the whole input.
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.4.0 (version code 10)
Affected Android/Custom ROM version
Android 14 (API 34)
Affected device model
Android emulator, Pixel 6 profile (1080 x 2400)
How did you install the app?
GitHub releases
Steps to reproduce the bug
- Open the app and go to
Unit converter. - Select
Speedand keep the defaultKilometer per hour -> Mile per hour. - Type
6then0on the number pad. The input shows60and the result shows37.282271534240038. - Tap the
Cbutton (resource idorg.fossify.math:id/btn_clear). - Look at the input field and the result field again, both immediately and after the page settles.
Expected behavior
After tapping C, both the input and the converted result should return to the neutral zero state (0 / 0). If the intended behaviour really is to delete a single character, the button should be a backspace (⌫) rather than being labelled C (Clear) - the label and the behaviour should match, or the wording should be updated so it does not conflict with what users expect from a Clear key.
Actual behavior
With 60 in the input, the result field shows 37.282271534240038. After tapping C, the input only becomes 6 and the result becomes 3.728227153424004 - the key removed the last digit instead of clearing the input. Keeping 60 without tapping C on the same Speed route shows the input and result refreshing normally, so the problem is limited to the clear action.
Screenshots/Screen recordings
https://github.com/user-attachments/assets/691e2f82-5c8c-4078-89ae-3bc30ff16014
Additional information
Package: org.fossify.math
Version: 1.4.0.
The FAQ says the C button removes one character at a time and that long pressing resets all fields, so the button already does what it is meant to. My problem is the label: C reads as Clear, so I expected it to empty the input and was surprised when it only removed the last digit.
- Dominant language
- Kotlin
- Stars
- 450
- Forks
- 57
- Avg merge
- 7d 35m
- Merged PRs (30d)
- 9
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/Calculator
-
feature request needs triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
FossifyOrg/Calculator#320 ·
Maintainers usually reply within 5 days
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Calculator#325 ·
Maintainers usually reply within 5 days
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
FossifyOrg/Calculator#313 · 1 reaction ·
Maintainers usually reply within 5 days
-
Rounding errorsOpenbug needs triage
Difficulty 3/5 1-2 days Newbie friendliness 50/100
FossifyOrg/Calculator#308 · 1 comment ·
Maintainers usually reply within 5 days
-
Percentual (%) operations not saved in historyPossibly taken @Guflly claimed this 69 days ago. Openbug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
FossifyOrg/Calculator#304 · 1 comment ·
Maintainers usually reply within 5 days
All issues in FossifyOrg/Calculator
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