WEB-446 Fix Websocket Reconnect - #139
Merged
Merged
Conversation
added 3 commits
August 7, 2026 09:35
Handle websocket state better to fix websocket reconnect after tab goes inactive.
chrishighet
marked this pull request as ready for review
August 13, 2026 13:05
chrishighet
requested review from
bakedpatato,
glenwperry,
ikennai and
wisc-gmv
August 13, 2026 13:05
chrishighet
changed the title
chrishighet
changed the title
wisc-gmv
approved these changes
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds some resiliency to the client so that when the websocket is left in a weird state due to the browser de-activating the tab it can recover and re-establish the websocket connection.