Issue metadata
Sign in to add a comment
|
WS tab incorrectly focuses on most recent frame
Reported by
germ...@gmail.com,
May 10 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Have more than one websocket connection. 2. Go to WS -> Select socket A -> Click on Frames. 3. Have a message come in for socket B. 4. Notice that Frames is now showing data for socket B. What is the expected behavior? 1. Have more than one websocket connection. 2. Go to WS -> Select socket A -> Click on Frames. 3. Have a message come in for socket B. 4. Focus should remain on frames for socket A What went wrong? It seems that devtools is now automatically giving focus to the most recent websocket frame of any connection, but the focus should remain on the selected websocket connection. It used to work this way, but changed within the last two weeks or so. Did this work before? Yes Chrome version: 58.0.3029.110 Channel: stable OS Version: OS X 10.12.2 Flash Version:
,
May 12 2017
Happens on my Windows and Ubuntu computers as well.
,
May 15 2017
There is no need for two websocket connections. Just receiving data in a websocket connection will change the focus. You can test this in https://www.websocket.org/echo.html I have attached a gif of the same (I did test by sending a echo message, but receiving a message will also have same effect)
,
May 17 2017
This is happening consistently for me. Impossible to debug websockets.
,
May 17 2017
Can confirm the issue, as reported here on SO: https://stackoverflow.com/questions/44013382/websocket-connections-deselecting-in-chrome-devtools-network-viewer/44015494#44015494
,
May 17 2017
I just tested this in 60.0.3102.0 and it seems to provide the correct behavior.
,
May 17 2017
Thank you for providing more feedback. Adding requester "ligimole@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 18 2017
Thank you for the report. That looks pretty inconvenient on stable. The issue is not reproducible on M59 Beta and M60 Canary, so the behavior should be back to normal soon when stable updates. cc'ing allada@ in case there are other workarounds.
,
May 18 2017
This workaround can be used till we get next build. http://stackoverflow.com/a/44016962/1358843 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, May 10 2017Components: Platform>DevTools>Network
Labels: Needs-Triage-M58 Needs-Feedback