Mobile networks/browsers can block wss:// upgrades even when the page loads (server verified: browser-style handshake gets 101). After 3 socket failures the header shows polling (5s) instead of a perpetual reconnecting; the REST poll keeps data correct. Also surfaces the browser's socket error message.
Frontend build + tests pass.
Mobile networks/browsers can block `wss://` upgrades even when the page loads (server verified: browser-style handshake gets 101). After 3 socket failures the header shows **polling (5s)** instead of a perpetual **reconnecting**; the REST poll keeps data correct. Also surfaces the browser's socket error message.
Frontend build + tests pass.
On some mobile networks/browsers the wss:// upgrade is blocked even though the
page loads (the server side is verified working: a browser-style handshake gets
101). After three socket failures the header now shows "polling (5s)" instead
of a misleading perpetual "reconnecting", since the 5s REST poll keeps all data
correct. The socket error handler also surfaces the browser's message.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Mobile networks/browsers can block
wss://upgrades even when the page loads (server verified: browser-style handshake gets 101). After 3 socket failures the header shows polling (5s) instead of a perpetual reconnecting; the REST poll keeps data correct. Also surfaces the browser's socket error message.Frontend build + tests pass.
Pull request closed