Issue metadata
Sign in to add a comment
|
Dev Tools jumps to websocket that received latest traffic
Reported by
kelvin.d...@onetouchdirect.com,
May 19 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36 Steps to reproduce the problem: 1. Open two web sockets 2. Make both websockets ping the server and the server reply immediately every second What is the expected behavior? What went wrong? Dev tools should not force you to another place. It makes it very difficult to collect whatever you need from the right frame within the specific websocket. Did this work before? Yes I cannot provide an exact date but I am sure that dev tools did not behave like this a year ago Chrome version: 50.0.2661.102 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 21.0 r0 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jonathan.garbee@chromium.org
, May 19 2016Status: Duplicate (was: Unconfirmed)