4 ms·
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.
by jchw 7y ago
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.
- XaspR8d 7y agoThe 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...)
- silon42 7y agoIt would be nice if it showed some info about compression.
- digitarald 7y agoDoes that bug I filed capture it? https://bugzilla.mozilla.org/show_bug.cgi?id=1567606 https://bugzilla.mozilla.org/show_bug.cgi?id=1567606
- bonestamp2 7y ago> it could inspect websocket connections that started before I opened the inspector window That's cool, and there is a way to do this in chrome in the right circumstances (like another tab/window spawned that tab/window). But if you just want it there as kind of a DVR then that's nice... I wish that was the default (at least up to some reasonable buffer size).
- digitarald 7y agoI'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
- toupeira 7y agoIt 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).
- RussianCow 7y agoWhere 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.
- toupeira 7y agoWhoops I apologize, looks like it's only the console prompt! I get that Ctrl+V might be disabled for security reasons, but is there a config flag to enable it anyway? And yeah for some reason Ctrl+Left/Right to jump around words, Ctrl+Shift+Left/Right to select words, and Ctrl+Backspace to delete a word, are disabled in the console prompt as well (they do seem to work in all the other DevTools input fields I can see). These are pretty ingrained in my muscle memory so I constantly bump into them. Also I'm on Linux, in case that matters.
- RussianCow 7y agoInteresting, sounds like you may want to file a bug report. I'm on Linux as well (Arch, Cinnamon) and all of those key combinations work for me.
- toupeira 7y agoThat's curious, they do work fine on another machine running Xfce so apparently it's related to Gnome. Filed a bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1591783 https://bugzilla.mozilla.org/show_bug.cgi?id=1591783, thanks!
- jjoonathan 7y agoI seem to be running across an increasing number of buttons that simply don't register clicks in Firefox. It's probably not FF's fault -- my money would be on webdevs leaning on chrome-only features -- but it does bring my Firefox session to a screeching halt and sends me back to chrome, usually after filling a form and trying to hit submit. It happens about once a week. That's probably way too vague to be helpful unless someone else knows what I'm talking about, but if nobody does, I suppose knowing that could help motivate me to isolate and reproduce the issue next time it happens.