What's your opinion of Firefox's new developer tools?

chrismonsanto · on Oct 4, 2013

Firebug is much better.

- Tools like YSlow and PageSpeed require Firebug.

- You can't disable the browser cache from FF devtools, which really sucks when you are trying to debug a broken redirect.

- When inspecting an element in FF devtools, :before and :after CSS properties will not be shown. I wasted many hours debugging a CSS refactor because of this (imagine going up the DOM, comparing computed CSS properties until you reach the root). Both Firebug and Chrome devtools will show :before and :after properties.

I think Firebug and the Chrome devtools are comparable in quality.

trycatch · on Oct 4, 2013

> When inspecting an element in FF devtools, :before and :after CSS properties will not be shown.

It was fixed recently. https://hacks.mozilla.org/2013/09/new-features-in-the-firefo...

cromwellian · on Oct 4, 2013

Can you even debug a web worker with Firebug? How about SourceMap support? The times when I've had to switch to FF devtools have been pretty painful. The profiling and tracing tools in chrome also seem lightyears better.

madeofpalk · on Oct 4, 2013

> Chrome devtools will show :before and :after properties.

And on that, I was plesently surprised to see Chrome will now display :before and :after psuedo elements in the DOM structure

frederickf · on Oct 6, 2013

The responsive design view is very handy. It switches the size of the view port without changing the size of the whole window. I still use firebug most of the time, but there are some issues with firebug you have to be careful of. See this post for an example http://perfectionkills.com/understanding-delete/#firebug_con...

barrkel · on Oct 4, 2013

The profiler is nice, a lot better than Chrome IMO.