Closed
Bug 986414
Opened 10 years ago
Closed 10 years ago
[Cost Control] Undesirable keyboard behaviour in data usage: user can enter multiple decimal points
Categories
(Firefox OS Graveyard :: Gaia::Cost Control, defect)
Tracking
(tracking-b2g:backlog)
RESOLVED
WORKSFORME
tracking-b2g | backlog |
People
(Reporter: maat, Unassigned)
Details
[Cost Control] Undesirable keyboard behaviour in data usage: user can enter multiple decimal points **PATH 1** P1) Usage app is opened for first time 1) open the usage app 2) in the setup sequence navigate to the 'Data Report and Alert' screen 3) turn 'Data use alert' on 4) select the 'When use is above' option 5) when the form opens replace the value in the field to 0.5 (it does not matter if the associated value is GB or MB) 6) now press the comma button again **ACTUAL 1** the user can add as many commas as they like, however the Done CTA is inactive so i cannot submit the value **EXPECTED 1** The user can only add one decimal place **PATH 2** P1) Usage app has been opened before 1) open the usage app 2) select the settings icon in the top right hand corner 3) scroll down to the 'Data Report and Alert' section 4) ensure that 'Data use alert' is turned on 5) select the 'When use is above' option 6) when the form opens replace the value in the field to 0.5 (it does not matter if the associated value is GB or MB) 7) now press the comma button again **ACTUAL 2** the user can add as many commas as they like, however the Done CTA is inactive so i cannot submit the value **EXPECTED 2** The user can only add one decimal place —DISCUSSION— It fairly standard practice to only allow one decimal place. We see this behaviour in Calculators for example. My advice would be to disable the dot button on the keyboard if a decimal place has already been input into the field. Again this is a standard approach to the solution than can be observed benchmarks such as calculators ———————— **Build information** hamachi-ICS. eng. master. B-105. Gecko-4841e29. Gaia-27c9ed6
Reporter | ||
Comment 1•10 years ago
|
||
I would propose that this is a serious UX bug for the reasons outlined in comment 0, therefore am nominating.
blocking-b2g: --- → 1.4?
Comment 3•10 years ago
|
||
Fixed on bug 988268
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•