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

Issue 717962 link

Starred by 2 users
Status: Fixed
Owner:
█ allada@chromium.org
Last visit > 30 days ago
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Expose socket frames over DevTools Network API

Reported by gb.shm...@gmail.com, May 3 2017 
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. In a DevTools' extension JavaScript file, add listener to network requests
2. Send a test WebSocket request / Receive a response
3. Observe the DevTools Network API listener

What is the expected behavior?
Socket frames need to be exposed for developers over DevTools Network API

What went wrong?
Socket frames aren't exposed over DevTools API

Did this work before? N/A 

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

Comment 1 by eostroukhov@chromium.org, May 3 2017

Owner: allada@chromium.org

Comment 2 by kavvaru@chromium.org, May 4 2017

Labels: TE-NeedsTriageHelp

Comment 3 by allada@chromium.org, Oct 3 2017

Status: Fixed (was: Unconfirmed)
Websockets are exposed here: https://chromedevtools.github.io/devtools-protocol/tot/Network/#event-webSocketFrameReceived

Thanks for the report though!
►

Sign in to add a comment