Is this not the current functionality in Developer edition?
It is. Firefox Developer Edition uses the beta channel, which is already on version 70.
Gotcha. Thought I was going mad.
Firefox’s New WebSocket Inspector
21–30 of 55 posts
Re: Firefox’s New WebSocket Inspector
#22Earlier quoted context omitted.
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.
> that might bog down or even crash devtools I'm not convinced - if that's true, then there's so many frames that clicking the websocket would crash devtools, which is equally unacceptable. In my experience people tend to use websockets in a not that dissimilar way to how they'd previously use pure HTTP requests, but now the server can instantly push data back too. If that is typical (hard to say) then it shouldn't b…
> I'm not convinced - if that's true, then there's so many frames that clicking the websocket would crash devtools, which is equally unacceptable.
Check out and financial trading website using websockets (for example the crypto ones). You'll see tens of messages per second. Example - https://www.bitmex.com/app/trade/XBTUSD
Re: Firefox’s New WebSocket Inspector
#23Binary WS data inspector with an ASCII decoder would be useful: the current trend is to use binary WS socket data to obfuscate/prevent scraping (e.g. NYSE.com real time quotes)
Re: Firefox’s New WebSocket Inspector
#24Finally! Soon I won't need to start Chromium to debug something as simple as websockets anymore.
I recently found out about the CSS tooling Firefox has for flexbox (they're quite hard to discover).
Another feature I sometimes use in Chrome is the ability to specify my own network throttling specs (based on measured throughputs of customers and users) instead of the default profiles. It's much less of an issue than the websockets but I hope that custom network profiles become a feature as well soon. So far none of them seem advanced enough to not necessitate a virtual instance of pfSense with a shaper (to allow for burst speed/packet loss/etc.) to reliably reproduce customer network behaviour but every advancement here is a step closer to ditching my clunky setup.
Re: Firefox’s New WebSocket Inspector
#25Great work! Gonna try it out!
BTW when could we have firefox be able to use the private client certificate from the MacOS's system keychain?
Have been switched back to FF as my personal browser for the past month, now this is the only thing blocking me from using it in my working environment.
Re: Firefox’s New WebSocket Inspector
#26Something I've had a really hard time with is profiling bandwidth usage over time. I'm happy that I can look at individual messages and see their size, but I want to watch how the KB/s changes over monitored time.
The unsatisfying answers from the Web are generally, "Use Wireshark." I don't think I should need to drop down to that layer.
Re: Firefox’s New WebSocket Inspector
#27Binary WS data inspector with an ASCII decoder would be useful: the current trend is to use binary WS socket data to obfuscate/prevent scraping (e.g. NYSE.com real time quotes)
Yes, this is upcoming next as binary preview is pretty bad without it.
Re: Firefox’s New WebSocket Inspector
#28Binary WS data inspector with an ASCII decoder would be useful: the current trend is to use binary WS socket data to obfuscate/prevent scraping (e.g. NYSE.com real time quotes)
Is there some common protocol that is used for binary communication, or is it all custom? Something like hexview or xxd would probably help generally.
Re: Firefox’s New WebSocket Inspector
#29Binary WS data inspector with an ASCII decoder would be useful: the current trend is to use binary WS socket data to obfuscate/prevent scraping (e.g. NYSE.com real time quotes)
Is there some common protocol that is used for binary communication, or is it all custom? Something like hexview or xxd would probably help generally.
Usually custom, that needs to be reverse engineered (with some help of usually minified JavaScript)
Re: Firefox’s New WebSocket Inspector
#30Earlier quoted context omitted.
I'd love to hear what other things come to mind regarding feature parity. We have been hitting a few of those out of the park lately and are slowly running out of obvious ones crossing fingers
It would be great if the DevTools input fields behaved like all other input fields in Firefox ;-) Things like Ctrl+C/V, Ctrl+(Shift+)Left/Right, and others I'm probably forgetting right now (am on phone).
Where don't they? I just did a quick run through the dev tools and all the input fields I used behaved exactly as I expected.