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

Firefox Debugger

mozilladevelopers.github.io

Post reply on HN
Print view View original

61–70 of 70 posts

Re: Firefox Debugger

#61

Post by sudeepto_dutta »

callahad wrote: post #60
sudeepto_dutta wrote: post #58

Earlier quoted context omitted.

Hello Sir, Pardon me if this is a silly question, but in the about:config page of Firefox Developer Edition the value for app.update.channel is aurora. But AFAIK, the aurora channel was stopped since April 18th of this month. This is the screenshot : https://imgur.com/r5Kcqb3

Aurora used to be a separate pre-beta, post-nightly release channel: Release In 2014, we rebranded Aurora builds to "Developer Edition" to give it better visibility and ship experimental features that we thought would be interesting to web and add-on developers. Earlier this year, we sped up our time-to-release by removing Aurora from the pipeline, but we kept it as a separate channel roughly at parity with Beta: Rel…

Thanks for the reply sir. I have one more question. I was very excited to use quantum, so ended up using developer edition. I am using it on my macOS High Sierra.

The battery usage and Energy impact that I observed from Activity Monitor application in macOS was very surprising.

Both parameters were quite high and the battery was draining very quickly. I don't have the screenshot. I tried searching for a solution like tinkering the about:config fields etc. but couldn't find any.

Re: Firefox Debugger

#64

Post by starik36 »

jpkeisala wrote: post #44

How does this compare to Chrome Developer Tools?

It's similar if you look skin deep. Differences emerge once you start using it on daily basis.

The coolest thing FF has over Chrome is the little [ev] icon next to an element that shows what events are connected to it. Saves me lots of time trying to track things down.

The coolest thing Chrome has over FF is that stepping through code is so much faster. There is no lag at all, while there is one in FF. It also has a "Search All" mode where it will look through all your code (html, js, css) to find a string.

Re: Firefox Debugger

#65

Post by wldcordeiro »

deltaprotocol wrote: post #49
shmerl wrote: post #34

Earlier quoted context omitted.

Compare this new dark to one that was there a few versions back. I'm talking about the older one. Example: https://support.cdn.mozilla.net/media/uploads/images/2016-09...

Fully agree with you. The old dark theme feels more comfortable (less contrast between colors). Each and every time I open the devtools now this thought crosses my mind.

The old theme had issues with accessibility due to that lessened contrast. There were some plans and PoC code made for custom theming though.

Re: Firefox Debugger

#66

Post by Macha »

starik36 wrote: post #64
jpkeisala wrote: post #44

How does this compare to Chrome Developer Tools?

It's similar if you look skin deep. Differences emerge once you start using it on daily basis. The coolest thing FF has over Chrome is the little [ev] icon next to an element that shows what events are connected to it. Saves me lots of time trying to track things down. The coolest thing Chrome has over FF is that stepping through code is so much faster. There is no lag at all, while there is one in FF. It also has a…

> It also has a "Search All" mode where it will look through all your code (html, js, css) to find a string.

This feature is called "Search Sources" in Firefox. https://imgur.com/U515D8X

Re: Firefox Debugger

#67

Post by Macha »

aviaro wrote: post #51

The thing I'd like to see is the ability to remove/edit cookies.

It's there. Storage > Cookies. If you don't see a storage tab, you may need to turn it in the DevTools settings.

Re: Firefox Debugger

#68

Post by prokaktus »

Firefox Debugger is amazing, but I have some problems with performance. If I enable DevTools, then entire browser (other tabs too) hanging for 1-2 minutes while page with DevTools is reloading. I think it may be because a lot async calls were performing, about couple hundreds (we use RequireJS and every sourcefile loaded through different request).

Re: Firefox Debugger

#69

Post by codefined »

neoeldex wrote: post #29
polack wrote: post #24

Slightly OT; What's the "Developer Edition"? > Build, test, scale and more with the only browser built just for developers. This is the only description I could find on their website. What's the difference to the normal version?

The developer edition is bit more bleeding edge than beta, but less than nightly. Nightly is updated daily. I'm not sure what the developer frequency is. But if your sporting it, you're getting the fresh features not entirely ready.

Isn't this incorrect? The developer edition appears to be built from the beta version. You get some alternate switches turned on, such as extensions no longer required to be signed & other stuff, but none of it is specifically new.

Re: Firefox Debugger

#70

Post by starik36 »

Macha wrote: post #66
starik36 wrote: post #64

Earlier quoted context omitted.

It's similar if you look skin deep. Differences emerge once you start using it on daily basis. The coolest thing FF has over Chrome is the little [ev] icon next to an element that shows what events are connected to it. Saves me lots of time trying to track things down. The coolest thing Chrome has over FF is that stepping through code is so much faster. There is no lag at all, while there is one in FF. It also has a…

> It also has a "Search All" mode where it will look through all your code (html, js, css) to find a string. This feature is called "Search Sources" in Firefox. https://imgur.com/U515D8X

It's there - sure. But it doesn't work well. Example comparison between Firefox & Chrome.

https://i.imgur.com/BFejDaf.png

Post reply on HN