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

61–70 of 74 posts

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#61

Post by javagram »

pwdisswordfish2 wrote: post #49
tty2300 wrote: post #42

Earlier quoted context omitted.

When will safari provide a VM image so developers can actually test things on it?

Why would you need to? Just test things on another WebKit browser, it will work just as well on Safari.

What actively-developed WebKit browsers still exist for Windows?

FWIW, the assumption that safari and some random WebKit browser will behave the same seems unsafe to me. The release version of safari will probably be on a newer/older WebKit edition and stuff like tracking protection might behave differently.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#63

Post by kaycebasques »

zachwood wrote: post #46
kaycebasques wrote: post #27

Earlier quoted context omitted.

FF and Safari are both shipping some great stuff that we don't have in Chrome DevTools. Canvas debugger: https://webkit.org/blog/8452/canvas-debugging/ Flexbox inspector: https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto... Fonts tab: https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto...

That's got nothing to do with Chromium becoming ubiquitous as far as market share goes. Which is bad for everyone.

Sorry, given that this is a thread about DevTools I thought the conversation was scoped to DevTools. Didn't realize we were talking about browser share at large.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#64

Post by ptasker »

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…

Yup, I also tried to use the debugging tools in the new FF Dev Edition with a larger React codebase and it's a bit buggy for sure.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#65

Post by mnm1 »

kaycebasques wrote: post #24
mnm1 wrote: post #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.

What makes you say that FF Console is lightyears beyond Chrome? (I write the Chrome DevTools docs)

Mainly the request/response logging. It's all in one place. I can click an xhr and it pops up right in the same window in a tabbed interface. I can see the request, response, headers, pretty json output if any. In chrome I click on an xhr, it takes me to a different tab where I have to scroll and find that request manually. I then have to switch back and forth manually if I need to go to other xhrs. Maybe this has changed in the last year? I don't know but that alone merited the switch.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#66

Post by digitarald »

chupasaurus wrote: post #41
hcs wrote: post #31

Earlier quoted context omitted.

Bug reports are welcome, it may very well be something about your setup that hasn't been reported yet: https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools&... (I'm a Mozilla dev but not involved with Devtools, though I know a few folks, happy to provide pointers if you need 'em)

They are handling bugs through Github issues too, everything is under DevTools org ( https://github.com/firefox-devtools )

Article author here. We are monitoring both, but are recently managing all our work in bugzilla.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#67

Post by jasonlaster11 »

kaycebasques wrote: post #23
hahawhat222 wrote: post #2

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

We (Chrome DevTools) have had inline breakpoints since at least January 2017: https://umaar.com/dev-tips/129-inline-breakpoints/ The human-friendly variable mapping is very interesting, though. We'd love feedback on how well it works out in the wild.

Happy to discuss collaborating on mapping variables. The current approach is based on re-parsing with babel, but we would like to extend source maps to include relevant mapping data.

https://twitter.com/auchenberg/status/1129435519727820800

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#68

Post by digitarald »

phreack wrote: post #53
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.

IntelliJ uses different adapters for Firefox and Chrome, so they might have side effects. We also touched a lot of our protocol APIs when adding column breakpoints, so I will reach out to see if we can improve.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#69

Post by digitarald »

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…

Article author here: You are describing a lot of issues that should be fixed. If you could try out 68 for a bit, you can help us confirm.

I will aim for another post going into more of the issues and how we fixed them and sharing some more frustrating breakage developers might have experienced and how we improved it.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#70

Post by digitarald »

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.

fyi, we are picking up the websocket work this summer; so first parts might show up in 69, latest 70.
Post reply on HN