Closed
Bug 929353
Opened 12 years ago
Closed 12 years ago
[Helix][Settings] Wifi always show "offline" while launch up settings app
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:-, b2g-v1.1hd affected)
People
(Reporter: atsai, Unassigned)
Details
While launch up settings app, the Wi-Fi status always show "offline".
Pre-condition:
Wi-Fi is connected
STR:
1. Launch up Settings App
2. Tap on Wi-Fi and check the connection status
3. Tap on Back button
4. Close the settings app by the window manager
5. Launch up Settings app and check Wi-Fi
Expected Result:
1. Wi-Fi is connected to pre-set AP and shows on the subtitle
5. Wi-Fi is connected to pre-set AP and shows on the subtitle
Actual Result:
1. "Offline"
5. "Offline"
[2013/10/21 Helix Testing]
Gaia: c829a2042594b6c3a4899ee27979799a0f301534
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/f7c657f6d019
BuildID 20131015042201
Version 18.0
| Reporter | ||
Comment 1•12 years ago
|
||
Could you please take a look of it, Evelyn? Thanks in advance.
Comment 2•12 years ago
|
||
On my device, it will show up after 3 sec. The problem here is: onstatuschange event is late on Helix. I suspect there is a porting issue.
Flags: needinfo?(ehung) → needinfo?(ttsai)
Updated•12 years ago
|
Flags: needinfo?(ttsai) → needinfo?(kli)
Comment 3•12 years ago
|
||
HD+ing this as device specific. Thomas/Kaizhen please update your findings.
Thanks
blocking-b2g: hd? → hd+
Comment 4•12 years ago
|
||
inari also got the same behavior as helix. I think we need to make sure how the setting app gets the wifi status when it is lunched first.
Flags: needinfo?(kli)
Comment 5•12 years ago
|
||
I think this is only not a good UX, we shouldn't display "offline" as soon as the setting app is lunched. The wifi status should be displayed according to wifi status event.
--- a/apps/settings/index.html
+++ b/apps/settings/index.html
@@ -2837,7 +2844,7 @@
<a id="menuItem-gps" class="menu-item" data-l10n-id="geolocation">Geolocation</a>
</li>
<li>
- <small id="wifi-desc" class="menu-item-desc" data-l10n-id="fullStatus-disconnected">offline</small>
+ <small id="wifi-desc" class="menu-item-desc"></small>
<a id="menuItem-wifi" class="menu-item" href="#wifi" data-l10n-id="wifi">Wi-Fi</a>
</li>
Comment 6•12 years ago
|
||
If it's just a UI polish, I don't think it's a blocker. flag hd? to get attention.
Al, is there anything we lost?
blocking-b2g: hd+ → hd?
Flags: needinfo?(atsai)
| Reporter | ||
Comment 7•12 years ago
|
||
I agree it's not a blocker, but we still need the HD+ to land on v1.1.0hd. Unless it's acceptable for partners to cherry pick the fix into their repo.
Thanks for finding root cause.
Leave the bug to triage to see if we need to provide a patch for fixing it in v1.1.0hd.
Flags: needinfo?(atsai) → needinfo?(wchang)
Comment 8•12 years ago
|
||
(In reply to Evelyn Hung [:evelyn] from comment #2)
> On my device, it will show up after 3 sec. The problem here is:
> onstatuschange event is late on Helix. I suspect there is a porting issue.
How long does it take to have the UI reflecting the correct status currently? 3 second sounds a bit long to update some UI...
Are there chances that it doesnt get updated due to some glitch?
Flags: needinfo?(wchang) → needinfo?(ehung)
Comment 9•12 years ago
|
||
OK I just checked this on a device, the UX is not bad provided users cannot attempt to 're-connect' when the UI says Offline.
Upon entering the Wifi page, the connected status is visible.
blocking-b2g: hd? → -
Comment 10•12 years ago
|
||
(In reply to Wayne Chang [:wchang] from comment #9)
> OK I just checked this on a device, the UX is not bad provided users cannot
> attempt to 're-connect' when the UI says Offline.
> Upon entering the Wifi page, the connected status is visible.
yes, I think so. Things we can do here is just hiding "offline" string and leave it blank, which is already done on master.
Flags: needinfo?(ehung)
Comment 11•12 years ago
|
||
per my comment 10, close it as won't fix on v1.1
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•