On 2/17/2017 3:02 AM, Patrik Flykt wrote:
A bigger point of failure than re-checking for online status is the
presence of a captive portal. When the online check fails, ConnMan
detects the captive portal and sends a RequestBrowser method call to
the Agent. If there is no Agent or the Agent does not implement this
feature, then the connection status stays as ready. I have not heard of
any Agent UI that implements RequestBrowser to this day, unfortunately
Point of information: CMST does implement RequestBrowser with its
Agent. When triggered a search of the users path is made looking for
common browsers and a dialog is shown listing those found with a request
to select one to continue the login process.
Just thought I'd let you know.