Good 

The useful part of the repro starts at 0:38. The 'Network not available' screen flashes.

+ Ben
+ Zach

This is because error screen is shown on the webview error:

"<webview>: The load has aborted with error -137: ERR_NAME_RESOLUTION_FAILED.", source: extensions::webViewEvents (283)

and it's closed on shill reporting that network is connected. Gaia is reloaded, another ERR_NAME_RESOLUTION_FAILED happens, another error screen, stc...

So we can either handle WebView errors in out code in a more granular way, or make shill use the given name servers to do a network test.

It might also be useful to include a word about possible name server failure to the error message.

Zach, Ben, WDYT?

We definitely need to handle this somehow, more for the case of mistyped custom name servers than for random text entry. Agree that adding some warning messaging is good too.

There is no simple way to 'make shill use the given name servers to do a network test'. This is something we need to handle correctly in the WebUI.

It seems like a bad proxy configuration or a network portal could have as similar problem? In general we can not assume that a connected network equates to an available internet connection.

We should probably also include error code/ID to the error screen.