<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jchw</author><text>Oh 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.</text><parent_chain></parent_chain></comment><story><title>Firefox’s New WebSocket Inspector</title><url>https://hacks.mozilla.org/2019/10/firefoxs-new-websocket-inspector/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>pimterry</author><text>This is really cool, but I&amp;#x27;m slightly sad that it looks like they&amp;#x27;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&amp;#x27;s selected.&lt;p&gt;Imo, it&amp;#x27;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.</text><parent_chain></parent_chain></comment><story><title>Firefox’s New WebSocket Inspector</title><url>https://hacks.mozilla.org/2019/10/firefoxs-new-websocket-inspector/</url></story>