Firefox’s New WebSocket Inspector
hacks.mozilla.org
Firefox’s New WebSocket Inspector
1–10 of 55 posts
Re: Firefox’s New WebSocket Inspector
#2Finally!
With such great dev tools for most other things, I've been looking forward to not have to use Chrome for websocket work.
Also, it seems we already see why competition is great, lots of cool features on the inspection.
Re: Firefox’s New WebSocket Inspector
#3The only reason I use Chrome for development is the custom formatters, any idea if there’s a plan to implement this in Firefox?
Re: Firefox’s New WebSocket Inspector
#4Oh my God, this has been such a long time coming. Debugging WebSocket connections has been one of the main reasons I’ve had to open up Chrome in recent memory. There might not be full feature parity but I think now Firefox’s dev tools are at least complete for my uses.
Re: Firefox’s New WebSocket Inspector
#5Oh my God, this has been such a long time coming. Debugging WebSocket connections has been one of the main reasons I’ve had to open up Chrome in recent memory. There might not be full feature parity but I think now Firefox’s dev tools are at least complete for my uses.
The websocket-monitor extension for Firefox was actually better for me than Chrome's baseline, since it could inspect websocket connections that started before I opened the inspector window.
(To be clear, I'm not asking it to save past connections/frames. I just want to see the new frames that arrive/depart after I open it...)
Re: Firefox’s New WebSocket Inspector
#6This is really cool, but I'm slightly sad that it looks like they've taken the same approach as Chrome: treat the whole websocket connection as a single item in the list of requests, and then show the frames within separately when it's selected.
Imo, it'd be much better to have a UI that interleaved full HTTP requests with websocket frames, so you can see the comparative timing of the both (and of frames across multiple WSs) rather than having to look at all of them separately.
Re: Firefox’s New WebSocket Inspector
#7Nice! When can I debug nodejs code in Firefox?
Re: Firefox’s New WebSocket Inspector
#8This is really cool, but I'm slightly sad that it looks like they've taken the same approach as Chrome: treat the whole websocket connection as a single item in the list of requests, and then show the frames within separately when it's selected. Imo, it'd be much better to have a UI that interleaved full HTTP requests with websocket frames, so you can see the comparative timing of the both (and of frames across multi…
Given the amount of traffic a websocket might see, that might bog down or even crash devtools by loading that tab when there's a lot of messages. At least maybe you can see some summary information this way, and it also clearly delineates between multiple websockets, or if you closed one and opened another.
Re: Firefox’s New WebSocket Inspector
#9The only reason I use Chrome for development is the custom formatters, any idea if there’s a plan to implement this in Firefox?
We have them in the backlog and had some conversations with users about them to scope them out. What are you using them for? We hear it a lot from the ClojureScript community.
Re: Firefox’s New WebSocket Inspector
#10Oh my God, this has been such a long time coming. Debugging WebSocket connections has been one of the main reasons I’ve had to open up Chrome in recent memory. There might not be full feature parity but I think now Firefox’s dev tools are at least complete for my uses.
The websocket-monitor extension for Firefox was actually better for me than Chrome's baseline, since it could inspect websocket connections that started before I opened the inspector window. (To be clear, I'm not asking it to save past connections/frames. I just want to see the new frames that arrive/depart after I open it...)
It would be nice if it showed some info about compression.