Inline breakpoints and human-friendly variable names are gamechangers! Looks like FF is going above and beyond Chrome devtools with this update.
Faster Smarter JavaScript Debugging in Firefox DevTools
11–20 of 74 posts
Re: Faster Smarter JavaScript Debugging in Firefox DevTools
#12Inline breakpoints and human-friendly variable names are gamechangers! Looks like FF is going above and beyond Chrome devtools with this update.
Re: Faster Smarter JavaScript Debugging in Firefox DevTools
#13Earlier 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.
Re: Faster Smarter JavaScript Debugging in Firefox DevTools
#14Re: Faster Smarter JavaScript Debugging in Firefox DevTools
#15Firefox 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.
Re: Faster Smarter JavaScript Debugging in Firefox DevTools
#16I ran into this last night, Chrome shows me what requests are going over websockets, FF does not.
Re: Faster Smarter JavaScript Debugging in Firefox DevTools
#17Firefox 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.
Let's see how the new JS debugger feels.
Re: Faster Smarter JavaScript Debugging in Firefox DevTools
#18It'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
#19Re: Faster Smarter JavaScript Debugging in Firefox DevTools
#20Inline breakpoints and human-friendly variable names are gamechangers! Looks like FF is going above and beyond Chrome devtools with this update.
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.