As of Firefox version 50, it seems that Firebug will no longer work as Mozilla are migrating to Firefox Devtools. The tab Tools/Web Developer has a ‘debugger’ option. See this page for a discussion on the migration. Read all the posts dated 19 November for further information. It seems to me that the option gives … Read more
Chrome 15 allows you to change the scope of the console. On the bottom of the console, next to the clear console button, there is a menu that says <top frame> which will give a list of available frames: Firefox has a similar feature currently in development: You can also navigate across frames using the … Read more
Firstly, everything in ziesemer’s answer is correct. This is all about JavaScript history There are a number of functions that are available in various browser’s devtools consoles. Collectively, the methods are known as the Command Line API(off-line) (new link) and they all originate from Firebug. Nowadays we just have parity across browsers because Firebug did … Read more
Firebug does not work anymore once multi-process Firefox (separate processes for the Firefox UI and the websites) is enabled. See the related post in the Firebug blog. You may be able to reenable Firebug by setting the preferences browser.tabs.remote.autostart, browser.tabs.remote.autostart.1 and browser.tabs.remote.autostart.2 to false via about:config. Though at some point this preference will be removed. … Read more
you can also check out the IE Developer Toolbar which isn’t a debugger but will help you analyze the contents of your code. Visual Studio will help with the debugging Fiddler should help analyse the traffic travelling to and from your browser
There is an option for that in Chrome’s inspector. Open the DevTools inspector (mac: Cmd + Shift + C , windows: Ctrl + Shift + C) Click on the Toggle device mode icon , located on the upper left corner of the DevTools panel. (windows: Ctrl+Shift+M, mac: Cmd+Shift+M). Click on the More overrides icon in … Read more
Been wondering the same for quite some time now, just gut-wrenching when your in-the-moment-freestyle-css’ing with firebug gets blown to bits by an accidental reload or whatnot…. For my intents and purposes, I’ve finally found the tool…. : FireDiff. It gives you a new tab, probably some weird David Bowie reference, called “changes”; which not only … Read more
The second line is giving you a SyntaxError because the { token at the beginning of it causes an ambiguity, the parser treats it as if it were a Block statement, not the start of an object literal. For example, a valid Block statement: { foo: ‘bar’ } The above looks like an object literal, … Read more
Yes they are different. View source shows you the original HTML source of the page. The inspector shows you the DOM as it was interpreted by the browser. This includes for example changes made by javascript which cannot be seen in the HTML source. Oh and this also counts for the developer tools that allow … Read more
Original answer: Check for the console object (created only with Firebug), like such: if (window.console && window.console.firebug) { //Firebug is enabled } Update (January 2012): The Firebug developers have decided to remove window.console.firebug. You can still detect the presence of Firebug by duck typing like if (window.console && (window.console.firebug || window.console.exception)) { //Firebug is enabled … Read more