Calculator: The C (Clear) button in the unit converter only deletes one character instead of clearing the input
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 58/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Kotlin
- Stelle
- 450
- Fork
- 57
- Merge medio
- 1g 19h
- PR unite (30g)
- 11
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di FossifyOrg/Calculator
-
Unit converter: Foot vs FeetApertafeature request needs triage
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
FossifyOrg/Calculator#320 ·
I maintainer di solito rispondono entro 1 giorno
-
feature request needs triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
FossifyOrg/Calculator#325 ·
I maintainer di solito rispondono entro 1 giorno
-
feature request needs triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
FossifyOrg/Calculator#313 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
Rounding errorsApertabug needs triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 50/100
FossifyOrg/Calculator#308 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Percentual (%) operations not saved in historyForse già presa @Guflly l’ha presa 81 giorni fa. Apertabug help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 25/100
FossifyOrg/Calculator#304 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di FossifyOrg/Calculator
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
lugassawan/swe-workbench#823 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 80/100
Droid-Deck/DroidDeck#1355 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
IronCoreLabs/ironcore-alloy#351 ·
-
Lovelace refine Taak
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
MinBZK/MijnOverheidZakelijk#1383 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
world-federation-of-advertisers/cross-media-measurement#4739 ·
I maintainer di solito rispondono entro 1 giorno