Issue metadata
Sign in to add a comment
|
"Offline" network throttling setting does not disconnect open WebSockets
Reported by
shinypla...@gmail.com,
Jul 11 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/602.1.39 (KHTML, like Gecko) Version/9.1.2 Safari/601.7.5 Steps to reproduce the problem: 1. Open a web page that uses a WebSocket, e.g. sign into a Slack team 2. Select “Offline” present from “Network throttling” dropdown 3. Observe that WebScoket remains open What is the expected behavior? WebSocket should be disconnected, the same as if the internet connection had been disconnected at the OS layer. What went wrong? WebSocket remains operational. Did this work before? No Chrome version: 51.0.2704.106 (Official Build) (64-bit) Channel: stable OS Version: OS X 10.11.5 Flash Version: 22.0.0.192
,
Jul 13 2016
I have the same issue with the "Offline" setting on Windows 10 with Chrome Version 51.0.2704.106 m. I am using sock.js for the websocket connection and it keeps working on the real websocket protocol although beeing in the offline mode.
,
Jul 14 2016
I spoke with the team about this. Yes we could make a work around for just offline/online events, it is part of the underlying problem outlined here: http://crbug.com/563644 We are not sure exactly how to handle this at this time, but it is something we want to fix.
,
Aug 25 2017
Not only it doesn't disconnect existing opened websockets, it even doesn't prevent new websockets to be opened. "Offline" setting also doesn't influence WebRTC PeerConnections - they still happliy work.
,
Sep 21 2017
,
Dec 13 2017
,
Dec 13 2017
,
Nov 9
,
Nov 9
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by alph@chromium.org
, Jul 11 2016Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)