New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 614021 link

Starred by 4 users
Status: Duplicate
Merged: issue 598076
Owner:
█ allada@chromium.org
Last visit > 30 days ago
Closed: May 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Can't focus on single websocket in dev tools

Reported by xander.d...@inin.com, May 23 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.0 Safari/537.36

Steps to reproduce the problem:
1. Open a page with two websocket connections with active messages in both
2. Try to select a websocket and scroll back in frame history

What is the expected behavior?
The selected websocket stays selected

What went wrong?
When the other websocket sends or receives a message, the selection changes, and the scrollposition in history is lost

Did this work before? Yes Before Chrome 50, I think

Chrome version: 52.0.2743.0  Channel: n/a
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 22.0 r0

This makes it impossible to inspect frames on a page with two websockets open.

Comment 1 by chrish...@gmail.com, May 23 2016 

A workaround is to open the filter on network requests, type in a filter to the websocket you want to watch frames for so that it doesn't switch away.

Comment 2 by eostroukhov@chromium.org, May 23 2016

Components: -Platform>DevTools Platform>DevTools>Network
Labels: -OS-Mac OS-All
Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)
You can see this issue with the attached page.
ws-test.html
1.5 KB View Download

Comment 3 by allada@chromium.org, May 23 2016

Mergedinto: 598076
Status: Duplicate (was: Assigned)
Although the version it says you are using (52.0.2743.0) it should be fixed, please try downloading Canary or the dev channel and see if it is fixed for you.

For now I am going to mark this bug as a duplicate but please reply here if Canary or dev channel does not have it fixed for you.

Thanks!
►

Sign in to add a comment