This is the first thing you should check when there's a problem. You can get to this by choosing the Error Console menu item under the Tools menu or using -jsconsole on the command line.
Allows you to stop a script at predefined breakpoints, inspect variables etc.. A Venkman Introduction explains its use.
Ctrl-Shift-I, you can inspect the page currently loaded in the browser.
Strict code checking
If you set the pref
Allows you to print text on the native console. Use
\n to output a newline at the end. To see anything, you need to set the pref
browser.dom.window.dump.enabled to true, e.g. in <about:config> (add new pref, it doesn't exist per default); and to have a native console at all under MS Windows, you need to start Firefox via firefox
.exe -console. Using normal JS object inspection, you can write a function that dumps a whole object, similar to this ddumpObject().
var lines = ;
for (var frame = Components.stack; frame; frame = frame.caller)
lines.push(frame.filename + " (" + frame.lineNumber + ")");
Original Document Information
- Author(s): Ben Bucksch
- Created Date: September 12, 2005, Last Updated Date: November 10, 2009
- Copyright Information: Portions of this content are © 1998–2007 by individual mozilla.org contributors; content available under a Creative Commons license | Details.