I think you'll be quite impressed with Firefox's developer tools again. I've been more and more unhappy with Chrome's tools, mostly the subtle changes of not having filters and things so readily available anymore. The Firefox tools are quite slick though. I don't even use Firebug anymore.
So glad I am not the only one noticing the filter change. That additional click to display the filtering options that Chrome introduced really made me start using FF more and more for work.
I think this dumbing-down approach Google is doing with all their apps and websites will only alienate more and more professionals out of using their platform.
(Chrome DevTools team here). We cleaned up the filtering as it was totally inconsistent across all panels. So now it introduces one more click, but felt like generally that extra click was OK. I think we can still improve the UX, however. Which panels do you most use filters on (and for what?) Console, Network?
Hey Paul,
I'm trapped on Chromium-30.0.1599.101 (same goes for similar Chrome version) because DevTools freeze for ~3 minutes after GWT's SuperDevMode recompilation on newer Chrome/Chromium. There is huge regression in performance after Chromium 32.x.xxxx.xxx. Chromium-30.0.1599.101 is the latest version without this problem on my distro.
I've tried to report this but you guys don't have proper bug tracker only form in the about menu.
99% of the time I just want XHR, so this change added an extra click every time I open dev tools to look at the Network panel (also this step can be laggy if you're in development and you have hundreds of separate requests for your scripts/stylesheets, which I never care about). So I could actually be in favour of hiding away the filters if I could just set a default filter? Or if it just remembered my last selection?
