Navigating away from the timer view orphans the websocket connection #458
Description
If you're connected to a WebSocket server and navigate away (e.g. by clicking the "Splits" button) the current connection gets orphaned. When navigating back, the server connection button displays there not being a connection, but the old connection is still alive in the background, so if you "reconnect" you're actually creating a second connection, which will cause splits to be counted twice (assuming your split server sends messages to all connected clients)