[GitHub issue by jds2501 on 2012-08-08T04:35:32Z, https://github.com/mozilla-b2g/gaia/issues/3242] ## Build * Device: Otoro * Gaia: 7a5162ef0f8e5329b679575a49446dfd055f02f0 * Mozilla Central: e0022230e076d1050f9d22b614c42632076e125b ## Steps 1. Connect to wifi to one router - wait until you are fully connected 2. Leave the range of the router, such that you no longer have wifi connection 3. Go to wifi page in the settings ## Expected The wifi page should indicate that you are not connected to any router. ## Actual The wifi page still indicates that you are connected to that router. A checkbox still appears in the wifi section too.

[GitHub comment by jds2501 on 2012-08-08T04:36:44Z] Screenshot - http://tinypic.com/r/2dj5cmg/6

[GitHub comment by evelynhung on 2012-08-08T09:14:28Z] because `autoscan` is not enabled in code for some reasons, so the network list won't automatically update itself. @fabi1cazenave

[GitHub comment by fabi1cazenave on 2012-08-08T12:33:25Z] `autoscan` has been disabled by a UX request. Re-enabling it would solve this issue, but that would raise other UX problems — e.g. it could be tricky to select a network from a list if the list is refreshed automatically, especially when networks are ordered by signal strength. Anyway, that issue should not be related to the `autoscan` feature. I’d suggest to update this Wi-Fi page when: * the wifi status has changed * the page has lost and regained visibility @lco, what’s your opinion on this?

[GitHub comment by lco on 2012-09-18T17:43:58Z] @fabi1cazenave I agree with your proposal to update the Wi-Fi page for the reasons you mentioned. It should also update when you leave the Wi-Fi Settings page and then re-enter it (that might be what you mean in your second point)

Will work on this.

Pointer to Github pull-request

Pointer to Github pull-request

Review ping?

Comment on attachment 670559 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/5782 R- because of small nits. Should be fast to fix.

Verified as resolved on Unagi Build ID:20121231070201 Unable to verify on Otoro, only have Unagi

Verified as resolved on Unagi Build ID:201301120702022 Unable to verify on Otoro, only have Unagi

(In reply to mlevin from comment #11) > Verified as resolved on Unagi Build ID:201301120702022 > Unable to verify on Otoro, only have Unagi That's probably fine for the verification actually.