Hacker News Reader

Comment by jchw | Hacker News Reader

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.

View on HN

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.

Does that bug I filed capture it? https://bugzilla.mozilla.org/show_bug.cgi?id=1567606

> 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).

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.

Whoops 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.

Interesting, 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.

That'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, thanks!

I 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.

A lot of the time that it happens to me, and I've bothered to check, it's always been some react code that's had errors.

It could be the different extensions you have installed. Often this happens with adblockers, so if you use incognito mode or another browser it would fix it.

Strangely my routers web admin will not load at all on firefox. Checking the console shows there is a js error about an undefined variable. Really wonder how they managed to stuff up the page that bad.

Chrome is usable as a standalone mini-IDE. You can open developer tools, go to sources, open a folder as a workspace and start making an actual webpage - from scratch. It can create, open, save and edit files.

When I change a CSS property in the Rules tab under the Inspector, and I press ctrl/cmd+z, it doesn't set the property back to what it was before I changed it. And obviously ctrl/cmd+y doesn't go forwards.

It's amazing how such a small change makes it so much more difficult to use the Firefox dev tools compared to Chrome. Sometimes I just want to toggle between CSS values and see what is changing, or undo a few changes I made.

Not a total fix, but I always just put a new rule under the one I'm replacing, and use the checks to enable (override) or disabled the rule.

Proper undo-redo is on the roadmap. It works in some cases but needs to work throughout the whole Inspector!

debugging iframes. I write lots of code in jsfiddle/codepen/stack overflow and Firefox fails to be able to debug.

We are looking into that right now actually to make that easier, maybe you could file a specific bug. Are you using the iframe-picker in Firefox and that isn't working as expected?

Does it work for you? Your comment seems to suggest it mostly works fine for you but for me. For me it's 100% unusable.

1. JSFiddle. Run a fiddle with a loop (setTimeout/setInterval/requestAnimationFrame). Try to find it in the debugger. Fail

2. Add a `debugger` statement in the loop. Watch as Firefox doesn't display the code in the debugger

3. Add a syntax error, see message in console, click link to code, firefox doesn't display code.

Reply on news.ycombinator.com