@Kyle: If no network is available, the network indicator should show it, I would think?
@Tony: I get the impression that treating "unknown" as "inaccessible" is not the right thing to do. From what I can glean, it appears that QNAM starts out in the "unknown" state and, once the first request has been made, settles into "accessible" or "inaccessible" accordingly. If that is the way it actually works, treating "unknown" as "inaccessible" would be exactly the *wrong* thing to do. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1502282 Title: "unknown" connectivity status problematic Status in The Savilerow project: New Status in unity-scopes-api package in Ubuntu: New Status in unity-scopes-shell package in Ubuntu: New Bug description: metadata provides a scope a network connectivity status enum with three possible states: * connected * disconnected * unknown Sometimes unknown is the current state. This is quite problematic because in general a scopes that queries the network (that is, most scopes) need to know whether there is network or is not network and depending on this either make the network queries or display an error message. A status of unknown connectivity leaves the scope with no valid option: * the scope could assume the network is down and provide the user an error message. But often the network is not actually down, so this interrupts the user's flow unnecessarily * the scope could assume the network is up, but this is dangerous if it is not up To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
