Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Calculator: The C (Clear) button in the unit converter only deletes one character instead of clearing the input

Open
#338 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
58/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile

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

bug needs triage
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
  1. Open the app and go to Unit converter.
  2. Select Speed and keep the default Kilometer per hour -> Mile per hour.
  3. Type 6 then 0 on the number pad. The input shows 60 and the result shows 37.282271534240038.
  4. Tap the C button (resource id org.fossify.math:id/btn_clear).
  5. 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
ignoreImageMinify ignoreImageMinify

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FossifyOrg/Calculator

All issues in FossifyOrg/Calculator

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.