Closed
Bug 818314
Opened 12 years ago
Closed 10 years ago
Does not reconnect to a known network after forgetting the one that we are trying to connect to.
Categories
(Core :: DOM: Device Interfaces, defect, P4)
Tracking
()
RESOLVED
INVALID
blocking-basecamp | - |
People
(Reporter: nbp, Assigned: chucklee)
References
Details
(Keywords: b2g-testdriver)
STR: - Connect to network A (add it to the list of known network) - Wait until sucessful connection - Connect to a secure network B with bad identifiers - Go to the bootom of the page (edit networks) - Remove the network B. - Get back to the network list. Seen: - Nothing happen. Expected: - Reconnect to network A (because this is a known network)
Comment 1•12 years ago
|
||
Chuck, do you have any time to work on this? The problem here is almost certainly that we use selectNetwork (which disables all other networks) and only re-enable the rest of the networks when we connect and when we explicitly disable the misbehaving network. We probably need to detect when the "user" (client of the wifi API) deactivates the network for us and re-enable the rest of the networks.
Assignee: nobody → chulee
Comment 2•12 years ago
|
||
Soft blocking - can still manually select and shouldn't happen that often.
blocking-basecamp: ? → -
Priority: -- → P4
Comment 3•10 years ago
|
||
I can't reproduce the bug on Flame and it's pending for a while. Let's close it.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•