In the generated HTML webapp, network errors are not handled in any user-visible fashion.
Found in b3fc442786b219746cf6487fc606ef1a77e94a90
Steps to reproduce
Here's a local example that simulates a flaky internet connection / server.
Generate docs.
Run cldoc serve. It pops up yet another browser tab, but that's something for another issue report. :-)
Kill cldoc serve (e.g. ^C).
Click on a link in the browser tab.
Expected results
A browser "network problem" page. This is the right approach because, in modern browsers, it will kick off network connection status monitoring and may automatically retry the GET when the connection comes back, sometimes before the user notices.
Barring that, a custom dialog explaining that something has gone wrong.
Actual results
Nothing. You can click the link all you want.
If you happen to browse with your JavaScript Console open you might see something like the following:
Failed to load resource: net::ERR_CONNECTION_REFUSED
In the generated HTML webapp, network errors are not handled in any user-visible fashion.
Found in b3fc442786b219746cf6487fc606ef1a77e94a90
Steps to reproduce
Here's a local example that simulates a flaky internet connection / server.
cldoc serve. It pops up yet another browser tab, but that's something for another issue report. :-)cldoc serve(e.g.^C).Expected results
A browser "network problem" page. This is the right approach because, in modern browsers, it will kick off network connection status monitoring and may automatically retry the
GETwhen the connection comes back, sometimes before the user notices.Barring that, a custom dialog explaining that something has gone wrong.
Actual results
Nothing. You can click the link all you want.
If you happen to browse with your JavaScript Console open you might see something like the following: