Live data from Hacker News

Faster Smarter JavaScript Debugging in Firefox DevTools

hacks.mozilla.org

11–20 of 74 posts

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#11

Inline breakpoints and human-friendly variable names are gamechangers! Looks like FF is going above and beyond Chrome devtools with this update.

As much as I like a Firefox, no inline/live editing of Javascript leaves things a bit frustratingly behind the curve. Even Edge Classic has that, and it's terrible.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#12

Inline breakpoints and human-friendly variable names are gamechangers! Looks like FF is going above and beyond Chrome devtools with this update.

Looks like they finally added resizable columns in the networks tab! https://bugzilla.mozilla.org/show_bug.cgi?id=1358414

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#13
post #7
post #4

Earlier quoted context omitted.

I heard that this was going to be a GSOC project this summer, but I'm not sure if that was approved or not.

Mozilla methodology: staffs should avoid well defined works so that volunteers, interns, and students can do them.

It’s not a bad strategy: just figuring out what to do can be much harder than getting it done (which can be more easily delegated). Architects (of old) made the big bucks in the days; now according to the google model they’ve all become senior engineers and the definition of and piecing off of work is much less formal (not to mention that it might go out to interns or the community rather the junior devs).

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#15

Firefox dev edition has been my go to lately, highly recommended if you do a lot of markup / css debugging. Being able to see outlines around elements as I hover / scan through the DOM easily doubles my speed.

Can you not do that with every browser's dev tools?

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#17

Firefox dev edition has been my go to lately, highly recommended if you do a lot of markup / css debugging. Being able to see outlines around elements as I hover / scan through the DOM easily doubles my speed.

I agree. Whenever I have something strange going on with CSS Grid or Flexbox layouts, the issue is usually easier to find with Firefox than Chrome.

Let's see how the new JS debugger feels.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#18
You know, I've been using Firefox Dev Edition since it was Firefox Aurora (or Beta, I guess?), and it's great to hear that they are improving the dev tools! But I have to ask this in the nicest way possible: does anyone else think the tools just don't work a lot of the time?

It's something I noticed especially when they switched to React. A few examples I frequently experience:

1) Stepping through TS frequently switches back to the source JS. 2) Breakpoints don't always go away, and sometimes a page reloads with an invisible breakpoint, that stops the code, but doesn't show up in the list of breakpoints, and doesn't seem to be removable. 3) Breakpoints don't always stop at the the right place. 4) After having the tools open for a while, the tab starts freezing for multiple seconds every few seconds (GC, according to the perf tab, so it's either my code or the dev tools)

This comes from a place of love, and I'll still always use FF over Chrome, but I really have to ask if anyone else experiences the same issues, or if it's perhaps my setup/code that causes the problems?

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#19
FF has had more solid console and debugging tools now for almost two years and it's one of the main reasons I switched completely from Chrome. It really is a superior, more reliable experience. And the console is light years beyond chrome. I definitely recommend it.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#20

Inline breakpoints and human-friendly variable names are gamechangers! Looks like FF is going above and beyond Chrome devtools with this update.

Those have worked for a while now? Like https://umaar.com/dev-tips/129-inline-breakpoints/

The bigger issue is when local variables aren't captured by the context when paused in chrome. I'm curious how the Firefox devtools handle that.

Post reply on HN