I configure noVNC to reconnect automatically, which works great, but there is a minor UX issue which makes it less useful. I am interested in opening a pull request with this feature, but want to check if the community would be open to merging this type of feature before putting the time into developing it.
When it's trying to reconnect, it goes through several states:
* "Connecting..." with a horizontal spinner
* "Reconnecting..." with "Cancel" button and horizontal spinner
* "Failed to connect to server" with red background which disappears 1 second
* and then it does this on loop, depending on my reconnect delay setting
As I am starting, restarting, fixing my servers, the time where my VM is down can span from a few seconds to several minutes. The longer my VM is stopped, the more distracting/annoying these reconnect states become.
Feature request: after reconnect fails once, switch it to a "Reconnecting" state with no moving/changing UI elements:
* "Failed to connect to server. Attempting reconnecting...." with "Cancel" button, (no spinner)
* no red "Failed to connect to server" red flash message
* no "Connecting..." w/ spinner message
If you do the above, the user can keep the reconnecting delay ms low (ie: fast reconnects), but user isn't impacted visually when the VM is down for a while.
Thanks,
Tom Hallett