Current Situation
Presently, if connection to a websocket is lost we log to the console. This is fine for debugging purposes, but for users it could be frustrating if the page simply stops working for what would seem like no apparent reason.
Proposed Actions
When a websocket disconnects we should add a model to the lower right of the screen explaining as much which will disappear after some time. What exactly is should should be configurable though so that different clients are able to hook into the Websocket's life-cycle events. Doing this would also address similar proposals.
Work Items
Current Situation
Presently, if connection to a websocket is lost we log to the console. This is fine for debugging purposes, but for users it could be frustrating if the page simply stops working for what would seem like no apparent reason.
Proposed Actions
When a websocket disconnects we should add a model to the lower right of the screen explaining as much which will disappear after some time. What exactly is should should be configurable though so that different clients are able to hook into the Websocket's life-cycle events. Doing this would also address similar proposals.
Work Items