I'm not sure if this is a bug or I'm doing something wrong. I'm doing some development work that that requires me to inspect frames on a websocket connect. I do this under developer tools and click on the websocket and then frame information. Every time I do something the sends new frames Chrome immediately changes to another headers of another request. So I keep having to click back on the websocket. It didn't used to be like this and is very frustrating. Has anyone else experienced this?
1 Answers
Related