Closed
Bug 829615
Opened 13 years ago
Closed 13 years ago
Explain state change when wifi/bluetooth/etc icons are toggled
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(blocking-b2g:-, b2g18+)
People
(Reporter: jhopkins, Unassigned)
Details
(Keywords: b2g-testdriver, unagi)
When one of the wifi/bluetooth/etc icons are toggled, the UI should briefly explain what the state has been changed to and fade out shortly after.
For example:
Toggling wifi 'on' should display "Wifi enabled" and 'off' should display 'Wifi disabled'.
This will be especially helpful when it's not apparent what an icon does. For example, it was unclear to me what the new [ $ ] icon does.
(Boot2Gecko 1.0.0-prerelease, Last updated: 01/11/2013 10:30am)
Comment 1•13 years ago
|
||
Switching flags per new usage for tracking? + tef? after retiring basecamp?
Updated•13 years ago
|
Component: Gaia → Gaia::System
Updated•13 years ago
|
blocking-b2g: tef? → -
Comment 2•13 years ago
|
||
Josh, can we have a UX spec for this, please? (or close as WONTFIX…)
Flags: needinfo?(jcarpenter)
Comment 3•13 years ago
|
||
The iconography and toggles have been updated since this bug was filed, so the issue is less severe than previous. I expect most users who play with these will know what WiFi and Bluetooth toggles do, and we generally prefer not to bombard the user with positive confirmation messages if we can help it. So we'd prefer not to issue alerts here.
That said, I'm adding Rob for needsinfo as he is working with Francis on a patterns review and in a better position to comment on their thinking for situations like these.
Flags: needinfo?(jcarpenter) → needinfo?(rmacdonald)
Comment 4•13 years ago
|
||
I agree with Josh's assessment. The status bar indicators already serve as a confirmation for the wi-fi, bluetooth and airplane modes in any case. Thanks!
Status: NEW → RESOLVED
Closed: 13 years ago
Flags: needinfo?(rmacdonald)
Resolution: --- → WONTFIX
| Reporter | ||
Comment 5•13 years ago
|
||
Agreed - the icons are better now than when the bug was reported.
Comment 6•13 years ago
|
||
Thank you all for the clarification!
You need to log in
before you can comment on or make changes to this bug.
Description
•