Firebug 3 and Multiprocess Firefox

https://hacks.mozilla.org/2014/12/firebug-3-multiprocess-firefox-e10s/

by bpierre • 12 years ago

116 24 12 years ago

hacks.mozilla.org

DrinkWater• 12 years ago

i am curious, what is the advantage of using Firebug instead of the built-in developer tools?

JohnBooty• 12 years ago

One advantage is that there are plugins, like YSlow from Yahoo, that are available for Firebug. Though the article notes that plugins don't currently work with the Firebug 3 alpha.

YSlow is pretty useful, both as a developer and when attempting to demonstrate potential problems with a site's performance to others in an objective way.

Besides: a plugin with its own plugins is just cool.

arenaninja• 12 years ago

I think Firefox Dev Tools may have reached parity with Firebug. Up until recently (~3 months), Firebug was superior in network, more informative in console when using console.log for objects, resizing, etc. Still, Firebug does have add-ons

Touche2• 12 years ago

Firefox Dev Tools still has some gigantic bugs that make it unusable for a lot of scenarios. For example, it doesn't show evaled code in the debugger. Which means anything that dynamically creates code (common in development) can't be debugged. Shumway (the Firefox flash compiler) for example.

Fuxy• 12 years ago

I use a number of plugins in firebug like YSlow and FireLogger that unfortunately don't work with the default Firefox developer tools.

I honestly wish they did since there are very few features I would miss from Firebug itself but the plugins add very useful features.

ep103• 12 years ago

Firebug is basically built to extend default FF dev tool capabilities. Its comparable to running chrome nightlies.

kyriakos4• 12 years ago

Firefox own developer tools won't log ajax calls in console. Firebug does. This and the fact that you need to open the settings tab to enable preserve log are my problems with Firefox tools keeping me on firebug.

nathanstitt• 12 years ago

I agree, that's the single feature that's always kept me loyal to Firebug. There's a bug open on that at: https://bugzilla.mozilla.org/show_bug.cgi?id=972655

I'm attempting to find time to assist with it, but haven't thus far. Perhaps throwing it out here will bring in additional assistance

eterm• 12 years ago

Personally I've switched back to dev tools in the developer edition, mostly because the ability to see which elements have events attached from the markup view is very useful.

makmanalp• 12 years ago

Hmm. What's the use case for ajax calls in the console instead of just switching to the network tab? Convenience?

illumen2• 12 years ago

Yeah. Why make people switch? Almost every app does ajax calls, so it's very useful to have that information there for almost every developer.

kyriakos4• 12 years ago

yes convenience, saves time switching back and forth. chrome didn't have this feature either but they recently added it (even though not as good as firebug's since when you click on the entry in the console it takes you to the network panel and hightlights the entry rather than opening it up automatically)

robbyt• 12 years ago

AFAIK, the built-in developer tools in FFox > v33 log ajax calls now.

findjashua• 12 years ago

what version are you on? I'm on 34.0, and they show up in the network tab.

fletchowns• 12 years ago

Network tab isn't the console though

__david__2• 12 years ago

Firefox dev tools most certainly do log ajax calls to the console. I just tested it in 34.0.5…

kyriakos4• 12 years ago

I am on v35 and it doesn't. It allows you to log all network events which fills up the console.

harpb• 12 years ago

Logging to the console with Firebug 3: http://cl.ly/image/0V1x2g253J3F/Image%202014-12-03%20at%202....

kyriakos4• 12 years ago

I'm aware of that but it logs everything without a way to filter (unlike the network tab)

Firebug 3 and Multiprocess Firefox

Related Stories