Skip to content

Give Feedback About Connection State #581

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 2 tasks
rmorshea opened this issue Jan 12, 2022 · 0 comments
Open
1 of 2 tasks

Give Feedback About Connection State #581

rmorshea opened this issue Jan 12, 2022 · 0 comments
Labels
priority-3-low May be resolved one any timeline.

Comments

@rmorshea
Copy link
Collaborator

rmorshea commented Jan 12, 2022

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

@rmorshea rmorshea added this to the 2.0 milestone Jan 12, 2022
@rmorshea rmorshea changed the title Give Feedback on Disconnect Give Feedback About Connection State Jan 12, 2022
@rmorshea rmorshea added priority-3-low May be resolved one any timeline. type: feature labels Jan 13, 2022
@Archmonger Archmonger modified the milestones: Luxury, Essential Jan 29, 2023
@rmorshea rmorshea removed this from the Essential milestone Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-3-low May be resolved one any timeline.
Projects
None yet
Development

No branches or pull requests

2 participants