Fix delayed WebSocket reconnection when screen is turned off#12
Open
Fix delayed WebSocket reconnection when screen is turned off#12
Conversation
…on mobile Chrome When the screen is turned off on mobile Chrome, setTimeout timers are heavily throttled. This causes the reconnecting-websocket to take a very long time to reconnect when the screen is turned back on. This fix listens for the Page Visibility API's 'visibilitychange' event and immediately triggers a reconnection attempt when the page becomes visible and the WebSocket is not in OPEN state. Agent-Logs-Url: https://github.com/opensumi/reconnecting-websocket/sessions/79d31669-ef8c-4f3e-9d8d-49f75e371e02 Co-authored-by: bytemain <[email protected]>
Copilot created this pull request from a session on behalf of
bytemain
April 12, 2026 09:13
View session
|
|
bytemain
approved these changes
Apr 12, 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
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.
Mobile Chrome aggressively throttles
setTimeoutwhen the page is hidden (screen off), causing reconnection delays of minutes instead of seconds.Changes
visibilitychange→visible, immediately callsreconnect()if the socket is notOPEN, bypassing any throttled timersclose()to prevent reconnection after intentional closuretypeof document !== 'undefined'); no-op in Node.js