I use Chrome or Firefox built in developer tools, however I still think Firebug fits my workflow the best. Unfortunately it's too slow to use.
I use Firefox Firebug to debug but would switch to Google chrome if I could customize the keyboard shortcuts. I need to activate and hide the 'developer tools > inspect Element', 1000 times a day. Google Chrome Developer Tools keyboard shortcut customization on Mac. To open Chrome dev tools with just F12 on a Mac: Open up System. Your contribution is very important. If you have a specific issue, like a bug or feature request, please post a detailed description of the issue, and we will do our.
The thing I miss the most is the inline display of AJAX call responses, and being able to write/run multi-line snippets of JavaScript (without ctrl+enter). Somewhat interestingly, Firefox built their entire add-on architecture because Joe Hewitt wanted dev tools (for debugging the actual browser moreso than websites), and Firebug was split off from Firefox and made into an add-on. A decade later, this has reversed and every major browser now ships with integrated dev tools. Shamelessly hijacking your comment to ask a question.is there any way (Chrome/Firebug, whatever) to somehow output to console or a log, all javascript execution (ie: as any function is executed, output the function name and the argument values).
I know there is some way to turn on debugging and breakpoints, but having very little expertise in javascript and no knowledge of the code I'm looking at, the ability to just dump all activity so I could sift through it later would be tremendously useful. I've had trouble with them. They don't include inline stack traces for errors, so you have to do a lot more digging to find what happened and where.
Also, in the Network panel, every refresh resets your filters so you have to select XHR every time if you don't want to see a bunch of.html/.js file requests (this may have been fixed in FF v30, haven't tested yet). There are just a number of really small issues other than those that when you add them up, make the dev toolbar a lot less useful than Chrome. That said, I like Firefox the browser much better than Chrome.
One thing that I found indicative of the 'depth' of Firebug is the very simple context menu item when you right-click a URL in the Network tab: 'Copy as Curl command' (the text may read differently, this is from memory). It creates a clipboard entry which contains a 'curl' command line with all the cookie/header/etc. Data that would be sent from your browser if you were to request that URL (via Ajax or whatever).
You paste that into your terminal and you can keep retrying indefinitely without having to click/interact with the web page at all. Hugely useful if you're debugging the server side of a client-server interaction.
I like the search feature in Firebug. Being able to search across all scripts/nodes/stylesheets is rad. Is Chrome Dev Tools' search that good yet? Every time I am working with another dev and want to search for a symbol, I tell the other devs to switch to Firefox/Firebug because Chrome Dev Tools is a mystery of hunting and pecking when it comes to search.
(Google is not the best at something-something search??) I cannot understand why other devs are so happy with Chrome. The Chrome timeline is rad when it comes to performance tuning, and maybe a lot of devs are light on the JS and heavy on the CSS.
I jump into Chrome, briefly, whenever I want to tune performance. All of the dev tools have quirks, bugs, and dumb UI usability issues, but when I want to work with a large codebase (which is every day of my life), I find Firebug works the best. I learn something new every day, thanks! I've always gotten tripped up by the fact that Command-F pulls up a local file Find toolbar when I've focused a JavaScript source page.
I assumed that was the extent of the Find capabilities Chrome offered. I'm 51% angry and 49% embarrassed that I never knew this!:) Agreed the Web Workers debugger in Chrome is very advanced and as I recall they had that available straight away when the Web Workers feature was first released. I think the Firefox/Firebug guys have only just added javascript console output for web workers in Firefox 30 and the debugger protocol for web workers is still in development. I agree that Chrome's developer tool suite is more comprehensive than other browsers. For my day to day development tasks, looking at network calls, inspecting html and debugging CSS/JavaScript, Firefox+Firebug is still the most user friendly and accessible to me.
For those that are still looking for ways to access Chrome's Developer Tools: To access the developer tools, open a web page or web app in Google Chrome. Then take one of the following actions:.
Select the Wrench menu at the top-right of your browser window, then select Tools - Developer tools. Right-click on any page element and select Inspect element. On Windows and Linux, press. Ctrl+ Shift+ I to open Developer Tools. Ctrl+ Shift+ J to open Developer Tools and bring focus to the Console. Ctrl+ Shift+ C to toggle Inspect Element mode. On OS X, press.
⌥+ ⌘+ I (Option+Command+I) to open Developer Tools. ⌥+ ⌘+ J (Option+Command+J) to open Developer Tools and bring focus to the Console. ^+ ⌘+ C (Control+Command+C) to toggle Inspect Element mode.