Live data from Hacker News

Firefox’s New WebSocket Inspector

hacks.mozilla.org

51–55 of 55 posts

Re: Firefox’s New WebSocket Inspector

#51

Earlier quoted context omitted.

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.

Re: Firefox’s New WebSocket Inspector

#52

Earlier quoted context omitted.

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

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.

Re: Firefox’s New WebSocket Inspector

#53

Earlier quoted context omitted.

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.

Re: Firefox’s New WebSocket Inspector

#54
post #3

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

I use it for Elm development. https://github.com/kraklin/elm-debug-transformer. Please let me know where it is discussed, so I can contribute.

Re: Firefox’s New WebSocket Inspector

#55

Earlier quoted context omitted.

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

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!
Post reply on HN