Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Faster Smarter JavaScript Debugging in Firefox DevTools

hacks.mozilla.org

Post reply on HN
Print view View original

51–60 of 74 posts

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#51

Post by vanderZwan »

seanmcdirmid wrote: post #13
sanxiyn wrote: post #7

Earlier quoted context omitted.

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

I can also picture it organically happening: if I were a core dev, would I focus on the issues "anyone" could pick up, or the ones that only someone as deeply invested into the code base as me would have any hope of untangling?

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#52

Post by styfle »

dlbucci wrote: post #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 switc…

The first three bugs you listed are related to source maps. I haven’t used Firefox in a long time but I have experienced the same behavior in Chrome and VS Code when debugging TypeScript. It turns out, there was a bug in the loader that was generating source maps. Perhaps your issue is tooling and not the browser?

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#53

Post by phreack »

dlbucci wrote: post #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 switc…

I actually have the opposite problem. For some reason, debugging JS with IntelliJ (where I'm most productive) doesn't work nicely on FF so I have to keep a Chrome tab open, and it's just unusable since it's determined to open a tab on Webpack's bundled file which is enormous and lags for like 10 seconds on each page reload. FF is most wonderful in comparison when I have to debug in the browser.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#54

Post by noisem4ker »

omnimus wrote: post #47
5350-uiop-1130 wrote: post #44

A few years ago, while working at an agency, I was using the Firefox Developer Edition to build the front-end for a website. I was presented with a very weird UI bug from the client that I could not reproduce whatsoever. It was driving me mad. After an hour or so of frustration I realised that the bug did not occur on Chrome or Firefox "Standard" Editions and was only occuring on Firefox Developer Edition. Now I know…

Af far as understand Canarys eqvivalent is Firefox Nightly. Firefox Development Edition is not beta it is just different flavour of FF.

Firefox Developer Edition is actually based on Firefox Beta, which is an intermediate release between regular Firefox and Nightly. Your equivalence still stands, however.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#55

Post by sciurus »

omnimus wrote: post #47
5350-uiop-1130 wrote: post #44

A few years ago, while working at an agency, I was using the Firefox Developer Edition to build the front-end for a website. I was presented with a very weird UI bug from the client that I could not reproduce whatsoever. It was driving me mad. After an hour or so of frustration I realised that the bug did not occur on Chrome or Firefox "Standard" Editions and was only occuring on Firefox Developer Edition. Now I know…

Af far as understand Canarys eqvivalent is Firefox Nightly. Firefox Development Edition is not beta it is just different flavour of FF.

Firefox dev edition is based on the beta channel.

(Disclosure: I work for Mozilla)

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#56

Post by dhimes »

philliphaydon wrote: post #32
dlbucci wrote: post #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 switc…

I much prefer Firefox dev tools over chrome. The only time I use chrome is web socket stuff. Debugging css grids in Firefox (which I learned this year) is amazing.

Chrome also has CSS media rendering debug capabilities. I couldn't find these on FF.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#59

Post by 5350-uiop-1130 »

vanderZwan wrote: post #50
newsbinator wrote: post #45

Earlier quoted context omitted.

To be fair, when figuring out bugs like that, if it doesn't appear in your dev environment, you'd definitely start by replicating the client's environment as closely as possible, especially their browser version (and possibly their OS for obscure stuff). It's safe (and wise) to develop in Dev editions of browsers, so long as you're ready to debug in mainstream editions when the time comes.

Trying to reproduce across browsers is good policy too, IMO

Agree with both points. My perspective at the time, although I was doing cross browser testing, was frustration from my expectations of the expected rendering behaviour between two browsers that I thought were the same, besides the addition of some new dev features.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#60

Post by 5350-uiop-1130 »

sciurus wrote: post #55
omnimus wrote: post #47

Earlier quoted context omitted.

Af far as understand Canarys eqvivalent is Firefox Nightly. Firefox Development Edition is not beta it is just different flavour of FF.

Firefox dev edition is based on the beta channel. (Disclosure: I work for Mozilla)

Thanks for clarification. I was not aware at the time, perhaps my oversight or it may have not been clear on the website - was a couple years ago so I can't recall.
Post reply on HN