UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.96 Safari/537.36

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.
3. Select one connection, expand 'Frames' tab
4. Receive the message from other (not actively chosen connection)

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.

Did this work before? N/A 

Chrome version: 58.0.3029.96  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

The bug was fixed once https://codereview.chromium.org/1839783007
But it happens for me in the latest chrome version