Closed
Bug 807954
Opened 13 years ago
Closed 13 years ago
Data usage in cost control: alarm doesn't turn on-off by tappin over the line, but changes the value
Categories
(Firefox OS Graveyard :: Gaia::Cost Control, defect)
Tracking
(blocking-basecamp:-)
RESOLVED
DUPLICATE
of bug 814371
| blocking-basecamp | - |
People
(Reporter: sonmarce, Unassigned)
Details
Currently alarm turns on-off by tappin over the line, but specs says it doesn't. This functionality must be removed in order to prioritize other more important funtionality: change the limit. Actually, the specs says that you have to tap+hold over the alarm line, but we have agreed to chage it just by a simple tap.
| Reporter | ||
Updated•13 years ago
|
blocking-basecamp: --- → ?
| Reporter | ||
Updated•13 years ago
|
Severity: normal → major
Updated•13 years ago
|
Flags: needinfo?(hello)
Updated•13 years ago
|
blocking-basecamp: ? → -
To clarify further, the wireframes specify a TAP and HOLD to turn a limit alert ON, but this is proving too tricky to understand so we should change it to just a TAP on the limit alert tab.
If the limit is OFF - a dialpad appears to set a limit level. If the limit is already ON - a dialpad appears to change the limit level.
Updated•13 years ago
|
Flags: needinfo?(hello)
Updated•13 years ago
|
Component: Gaia → Gaia::Cost Control
| Reporter | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•