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

Steps to reproduce the problem:
1. Connect to multiple WebSocket servers at one time (at least 2)
2. Navigate to the Network tab of the Developer Tools
3. Click the 'WS' filter
4. Select one of the connections
5. Note what happens when the selected WebSocket receives a new frame from the server.

What is the expected behavior?
The frame list should be updated and the selected WebSocket connection should remain selected.

What went wrong?
The selected connection changes to the previous one in the list.  This makes it very difficult/impossible to view received data when the WebSocket connection is receiving ping/pong commands consistently.

Did this work before? N/A 

Chrome version: 58.0.3029.96  Channel: stable
OS Version: 10.0
Flash Version: 

The same behavior seems to happen when only one WebSocket connection is active and the 'All' filter is selected, but it was easier to create steps to follow with multiple connections.