Public bug reported:
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
** Affects: savilerow
Importance: Undecided
Status: New
** Affects: unity-scopes-api (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502282
Title:
"unknown" connectivity status problematic
To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
