Hacker News Reader

Comment by AnonHP | Hacker News Reader

Good to hear the reaffirmation from Mozilla that the blocking WebRequest API would be retained. A little over three years ago, Mozilla had promised that it wouldn’t just blindly follow Google on Manifest v3 to the letter. [1]

Considering that uBlock Origin works best and can do the most in Firefox with this continuing support, I’m glad Mozilla is still walking the talk on this one.

We need at least one browser that makes the web usable, and that might as well be Firefox with uBlock Origin.

Edit: Oops. Missed providing the link reference below earlier.

[1]: https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest...

View on HN

I really need to learn the Firefox debugger. My years of chrome debugger muscle memory has tied me to that product (at least for work which is 95% of my desktop browsing)

Personally I’m a mobile personal browser person which is safari. I can’t stand to be at a computer after a day of being at the computer.

Can you give an example of a feature that's so different or missing in Firefox devtools?

The only differences that come to my mind are super minor (chrome logging 400er requests to console, Firefox having more advanced grid/flex debugging. I'm kinda interested if I'm missing a super obvious feature that's commonly used.

If he's anything like me, it's just the muscle memory part. My understanding of JavaScript grew basically alongside the evolution of the Chrome DevTools, so there's quite a lot of subconscious navigation that just feels more intuitively, to me, in Chrome.

It's also a psychological bond to a certain extent, having relied on them during stressful times in my career... before that I had only FireBug and that served a similar purpose but didn't teach me quite as well and did never reach the status of "if the Chrome Devtools are open, I can understand what's going on here"-sense of security & confidence.

Yeah you can get over that in a few months. It is annoying though during the process. I switched a year ago.

Spot on. Every time I want to do X in Firefox and it takes me more than a few seconds to figure it out I get frustrated and use chrome. I do need to break this bad habit though. Maybe I’ll try again this week!

My favourite is ctrl+shift+l to clear the console as ctrl+l focused the URL bar. Damn it, guys. I only use chromium for work, though. The tools are somewhat easier to use

Performance tab in Chrome is miles better than in Firefox.

I think the biggest one for me is less a case of it being missing, more Chrome's implementation being better, and that's the Timeline tab. Firefox not only doesn't implement it natively (redirecting you to a web app at `profiler.firefox.com`), it also lacks screenshots, dropped/rendered/frame durations.

Overall, it also seems less accessible to me. It may well be that it's much more powerful in some respects, but I've never got my head around it enough to work that out.

I do very much rate its Memory Tree Map view, though. Big advantage over Chrome for rapid debugging of where memory goes.

Mobile debugging using a real handheld? I'm using the FF devtools extensively, I only have to switch to Chrome when some weired mobile issue arises.

Changing latency and throughput independently to any value.

Sometimes stack traces are missing in the console which Chrome does show.

Firefox Dev tools are better. At least for messing with styles and html

It's CSS Grid/Flexbox inspector is really nice. Does anyone use CSS grid/flexbox?

Firefox DevTools are better for some things (styles, accessibility tree, network "Edit and Resend") and Chrome's are better for others (editing local files in the DevTools)

I use Firefox for web development (I got used to using it in the Firebug days and never switched). On the occasion I’ve had to use the chrome developer tools I’ve had no problems since they are so similar.

If there are things that are missing it's worth asking for them if there isn't an equivalent.

I always do web dev on Firefox. I worry that developing on Chrome could lead to accidentally breaking Firefox support. But I think the opposite is much less likely.

My experience is that Firefox sometimes fixes the errors I create. Which is bad.

For example, document.querySelector("input[type=text") (note the missing ]) worked in Firefox but didn’t in Chrome. Or something similar to this.

Nothing stops you from developing on Chrome and using Firefox for general web browsing.

Presumably, you don't need an ad blocker to test and debug your own code, unless you are testing specifically for ad-blocking browsers. And if you are doing things properly, you should be testing on both browsers anyways, at least as a final step.

"Usable" is an overstatement, but we at least gotta fight the fight.

Reply on news.ycombinator.com