Issue metadata
Sign in to add a comment
|
Auto switching websocket connections
Reported by
l.meliki...@gmail.com,
Mar 8 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Firefox/45.0 Steps to reproduce the problem: 1. Open a website that has more than one websocket connections. 2. Open devtools and go to Network tab and select WS to see websocket connections only (reload the page). 3. Select one connection. There must be some messages received from server in these channels. What is the expected behavior? Do not auto select another connection. What went wrong? When there are new messages in another connection it is auto selected. It's not possible, for example, to see frames only for one connection without interruptions. Did this work before? N/A Chrome version: 49.0.2623.75 (64-bit) Channel: stable OS Version: OS X 10.11 Flash Version: This is very annoying because I'm unable to monitor frames only in one connection without interruptions every time other message is received somewhere.
,
Mar 10 2016
Hi, this bug is a major issue for us at blab.im. Basically we now can't look at our websocket frames anymore in chrome. To reproduce - open network inspector and enter a live blab which will have two websockets connections (one to a third party vendor). Try to look at frames on the "ws" websocket connection. You won't be able to as there are frames sent on the other connection and only those are displayed... It feels like this bug was introduced with the "Prettify frames data for websockets" feature: https://bugs.chromium.org/p/chromium/issues/detail?id=478624 See this in both: Version 49.0.2623.87 (64-bit) Version 50.0.2661.18 dev (64-bit) thank you and best regards, Florian
,
Mar 15 2016
This bug makes it almost impossible to debug our app which has 3 WebSockets constantly connected. Any time you're trying to view the connection frames the selection switches to another connection. Had to downgrade to old Chromium... Please fix ASAP.
,
Mar 15 2016
The same for me, please fix ASAP.
,
Mar 16 2016
I always monitoring WS network frames. Used for data debugging. please fix ASAP.
,
Mar 21 2016
Can't work with WebSockets, really need a fix for this.
,
Mar 31 2016
Same problem here...
,
Mar 31 2016
Temporary "fix" , maybe could help with ws apps debugging: filter websockets by name in dev tools.
,
Apr 9 2016
,
Apr 19 2016
Same here. This is SUPER frustrating and annoying.
,
May 13 2016
Chrome Version 50.0.2661.102 (64-bit) chromium Version 50.0.2661.94 Ubuntu 16.04 (64-bit) have the same bug. This is SUPER SUPER frustrating and annoying.
,
May 13 2016
This bug was fixed here: https://codereview.chromium.org/1839783007 It takes around 2 months for minor patches to hit stable. You can use our nightly build called "Canary" to see if a bug was fixed bug not landed on stable yet. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by alph@chromium.org
, Mar 8 2016Owner: alph@chromium.org
Status: Assigned (was: Unconfirmed)