Closed Bug 720176 (WSConsoleLogging) Opened 12 years ago Closed 5 years ago

WebConsole should be able to log WebSocket messages

Categories

(DevTools :: Console, enhancement, P4)

enhancement

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: sonny, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: [sudweb][websocket])

Would be great if the WebConsole could logs WebSocket in/out messages. Not juste the http handshake/upgrade.
Since the websocket connections are persistent, I don't really see how that could look like. But being able to debug websockets would be awesome.
As I see it there would be logs for socket opening, message in, message out, socket close, socket error.
That can be very very noisy. And websockets use streams. There is not actual "message in" events. But being able to expand the current content of the stream as logs can be interesting. But I am not sure this should be part of the Console. Maybe it should be part of a Network-dedicated tool.
+1 for this bug.
I am using socket.io in a project and the current devtools are of no help to understand what has been sent to the server.
If other devs come in this bug, the workaround I have found is to go in about:config and set network.websocket.enable to false (this disable the feature browser-wise, so re-enable when you're done testing).
Whiteboard: [sudweb]
Priority: -- → P3
We need this, but can't get to it right now. Marking P3.

Filter on GUNGNIR.
Whiteboard: [sudweb] → [sudweb][websocket]
Rob: WebSocket support should find it's way into the netmonitor as well, right? Should we track a netmonitor UI implementation in a separate bug?
Flags: needinfo?(rcampbell)
(In reply to Jeff Griffiths (:canuckistani) from comment #6)
> Rob: WebSocket support should find it's way into the netmonitor as well,
> right? Should we track a netmonitor UI implementation in a separate bug?

yes please.
Flags: needinfo?(rcampbell)
Blocks: 765651
Chrome do log websoket messages, but for me using Chrome is not a long term option. Maybe this will be one of the feature included in upcoming Browser for Devs #Fx10 ? This should definitively have a higher priority from a web developer perspective.
This needs to be evaluated, is this still valuable if we include WS data in network panel?
Alias: WSConsoleLogging
Severity: normal → enhancement
Should this linked to a netmonitor bug to show websockets messages in Netmonitor ? Or do we only want to have webSockets as a web extension ?
Flags: needinfo?(odvarko)
(In reply to Nicolas Chevobbe [:nchevobbe] from comment #10)
> Should this linked to a netmonitor bug to show websockets messages in
> Netmonitor ? Or do we only want to have webSockets as a web extension ?
This feature should be part of the new WebSocket Monitor extension.
(it's already linked to WSInspectorMaster, bug 885508)

Honza
Flags: needinfo?(odvarko)
We plan to create an API for WebExtension to consume WebSockets information. If this data is not directly visible in the netmonitor, I'd argue that we shouldn't show it in the WebConsole as well.

I don't think this bug should be a blocker to Bug 885508, but the opposite.
No longer blocks: network-websocket-inspector
Priority: P3 → P4
Product: Firefox → DevTools
Closing as we want a dedicated tool for webSockets, and not show messages in the console
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.