Depurador

O Depurador Javascript permite-lhe percorrer o código JavaScript e examinar ou modificar seu estado para ajudar a localizar bugs.

Você pode usalo para depurar código executando localmente no Firefox ou executando remotamente, por exemplo em um dispositivo Firefox OS ou Firefox para android. Este guia assume que você está depurando localmente, mas é na maioria das vezes aplicável para depuração remota também. Veja o guia para depuração remota (inglês) para as diferenças.

Para Abrir o Depurador selecione "Depurador" no submenu do Menu do Firefox (ou menu de Ferramentas , se você exibir a barra de menu ou estiver no Mac OS X), ou pressionando Control-Shift -S (Command -Option- S se estiver no Mac OS X) .

A Toolbox aparece na parte inferior da janela do navegador , com o depurador ativado. Aqui está o que aparece quando você abri-lo primeiro:

E aqui está o que parece no meio de uma sessão de depuração:

Neste guia , vamos primeiro ter um rápido passeio de interface do usuário do depurador, em seguida, iremos descrever como executar algumas tarefas comuns de depuração .

A Interface do usuário para depurador

A  UI (Interface de Usuário) do depurador é dividida em seis seções principais, que abrangerá uma de cada vez:

• barra de ferramentas
• lista código fonte 
• painel de lista de chamados (novo no Firefox 29)
• painel de fontes
• painel de variáveis
• painel de eventos

Painel códigos fontes

O painel de lista de origem, lista todos os arquivos de origem JS carregados na página, e permite que você selecione um para depuração. Apartir do Firefox 29, a origem do painel de lista, compartilha sua tela de imóveis com a pilha de chamadas do painel, e você pode usar as guias na parte superior do painel para alternar entre elas.

Arquivos de origem são agrupados sob diferentes rubricas de acordo com onde eles são carregados. Você pode selecionar qualquer um desses arquivos e eles serão carregados para o painel de código.
Quaisquer pontos de interrupção que você definiu em um arquivo de origem estão listados no painel da lista de origem sob o nome de arquivo. A caixa de seleção ao lado de cada ponto de interrupção permite você ativá-lo / desativá-lo. Clicando com o botão direito na entrada do ponto de interrupção na lista, mostra um menu de contexto permitindo-lhe:

• ativar, desativar ou remover este ponto de interrupção, todos os pontos de interrupção, ou todos os pontos de interrupção exceto este
• fazer este ponto de interrupção condicional (ou editar as suas condições, se já for condicional)

The three icons at the bottom of the source list pane enable you to black box a source, pretty-print minified JS files, and toggle all breakpoints on or off.

Black boxing

The eyeball at the bottom-left of the pane is a button that enables you to black box the currently selected source. Black boxing is useful for sources which you are using but not debugging, such as libraries like jQuery. If a source is black boxed, it's assumed to be of no interest to the debugger: any breakpoints in it will be disabled, and the debugger will skip through it when stepping through code.

In versions of Firefox before 27, the eyeball icon appears next to the source file name when you hover over it.

Pretty printing

The pair of braces {} enable you to pretty-print files that have been minified, to make them more readable.

Toggle all breakpoints

The button lets you disable all breakpoints, or reenable them, in a single action. This makes it easy to switch between running a program and stepping through it.

Call stack pane

The other tab on the left-hand side of the debugger displays a vertical call stack:

Each row represents a level in the call stack, with the current stack frame on top. The row shows the name of the function currently executing, and a link to its source file and line number.

Source pane

This shows the JavaScript file currently loaded. Breakpoints have a blue circle next to the line number, while breakpoints you've hit have a green arrow inside the circle:

In the source pane, the context menu enables you to:

• set a breakpoint
• set a conditional breakpoint
• add a watch expression for the selection
• search or filter using the script filter

Variables popup

If you hover the mouse over a variable in the variables pane, a popup appears showing you that variable's current value:

This enables you to get a quick look at a variable without having to open and search the Variables pane.

Toolbar

The toolbar consists of four sections:

• a row of buttons to control movement through a script
• a visualisation of the call stack
• the script filter
• buttons to expand/collapse the variables and events panes and to control debugger settings

The four buttons on the left perform the following functions:

• Pause/Resume (F6): pauses or resumes execution of the script you're debugging. When it's blue and "pressed", as above, that means the script is paused, either because you've paused it with this button or because you've hit a breakpoint.
• Step Over (F7): steps across the current line of JavaScript code.
• Step Into (F8): steps into the function call on the current line of JavaScript code.
• Step Out (Shift-F8): runs the script until the current function exits.

The call stack visualisation shows the call stack at the point execution is paused.

Script filter

The script filter enables you to search in all three of the debugger's panes. By prefixing the filter expression with one of several special characters, the filter provides various different functions.

These options are shown in a pop-up when you click in the filter, and they're also accessible from the context menu in the source pane. Prefixes can be combined to form more powerful queries, like "file.js:12", which will open file.js and highlight line 12, or "mod#onLoad", which will find the string onLoad in all files containing mod in their name. Hitting the Enter key after searching will cycle between the matches found.

Debugger settings

At the right-hand end of the toolbar are two more buttons. The first of these shows and hides the variables and events panes, and the second enables you to toggle various debugger settings:

Variables pane

The variables pane is where you can examine, and modify, the internal state of the script as it's executing:

The variables pane shares its screen real estate with the events pane, and you can use the tabs at the top of the pane to switch between them.

Examining variables

Variables are grouped by scope: in Function scope you'll see the built-in arguments and this variables as well as local variables defined by the function like user and greeting. Similarly, in Global scope you'll see global variables you've defined, like greetme, as well as built-in globals like localStorage and console.

Each object can be expanded using a disclosure triangle to show its members.

Pointing your cursor at a variable's name displays a tooltip that provides additional information about the variable; for example, pointing at the greeting object displays "configurable enumerable writable". See Object.defineProperty() for details on what these property descriptors mean.

You can filter the variables that are displayed, either by using the "*" modifier in the script filter, or by typing into the filter variables box, if you have enabled this in the debugger settings.

Modifying variables

You can change a variable's value by clicking on its current value and entering a new one; for example, if you click on "Hi, Dr. Nick!" next to greeting, you can edit the value.

Watch expressions

Watch expressions are expressions that are evaluated each time execution pauses. You can then examine the results of these expressions. These are useful in that they let you inspect invariants in your code that you know are there but aren't necessarily in the code ready for inspection. To add a watch expression, click in the box that says "Add watch expression" and enter a JavaScript expression whose output you'd like to monitor as you step through code.

Then start running your code. The watch expression does nothing until you begin to step through your code, so nothing happens until you reach a breakpoint. At that point, a box showing your active watch expressions and their current values will appear:

You can step through your code, watching the value of the expression as it changes; each time it does, the box will flash briefly yellow. You can remove a watch expression by clicking the "x" icon next to it, and, of course, you can have more than one watch expression at a time.

Highlight and inspect DOM nodes

If you hover over a DOM node in the Variables pane, it will be highlighted in the page:

Also, a target icon will appear next to the variableIf you click on this target, the Inspector will open with this DOM element selected.

Events pane

The events pane lists all DOM events that currently have listeners bound from your code:

It shares its screen real estate with the variables pane, and you can use the tabs at the top of the pane to switch between them.

It groups events by type. The screenshot above shows four types: Interaction, Keyboard, Mouse, and Navigation. Under each type it lists all events which have listeners in your code, with the following syntax:

[event name] on [event target] in [source file]

If you check the checkbox next to the event, the debugger will break at the first line of the event's listener. If you check the checkbox next to the event type, then the debugger will break for any of the events listed under that type.

How do I...?

Open the debugger

To open the debugger, select "Debugger" from the Web Developer submenu in the Firefox Menu (or Tools menu if you display the menu bar or are on Mac OS X), or press Control-Shift-S (Command-Option-S on the Mac).

Find a source file

When the debugger's open, all the JavaScript source files are listed in the source list pane. You can browse the list to find the one you want, or search for a particular file using the script filter.

Find inside a file

To find a function, search for a string, or jump to a line in a file open in the source pane, you can use one of the special modifiers in the script filter.

Set a breakpoint

To set a breakpoint in a file open in the source pane:

• either click on the line number for the line you want to break at
• or activate the context menu while on the line you want to break at, and select "Add breakpoint"

Each breakpoint is shown in two places in the debugger:

• they're listed in the source list pane underneath the file's name
• the line in the source pane is marked with a blue circle

The screenshot below shows breakpoints at lines 3 and 10 of the file:

Set a conditional breakpoint

To set a conditional breakpoint, activate the context menu while on the line you want to break at, and select "Add conditional breakpoint". Then enter the conditional expression in the popup that appears:

To edit the condition, or to add a condition to a normal breakpoint, activate the context menu and select "Configure conditional breakpoint":

Disable a breakpoint

To disable a breakpoint:

• either: uncheck the check box next to the breakpoint's entry in the source list pane
• or: activate the context menu while your mouse pointer is over the breakpoint's entry in the source list pane, and select "Disable breakpoint"

Disable/enable all breakpoints

To switch all breakpoints on or off, use the "Toggle all breakpoints" button in the Source list pane.

Break on a DOM event

If you're listening to a particular DOM event, you can tell the debugger to break when the event is triggered without having to track down the listener and set a breakpont manually.

First, open the events pane: click the button in the toolbar that opens the shared variables/events pane, then click the tab labeled "Events". The events pane will list all events for which you have assigned a listener:

Then check the box next to the event you want to break at.

When the event is triggered the code will break at the start of your listener.

Step through my code

When your code stops at a breakpoint, you can step through it using the four buttons on the left of the toolbar:

In order, the buttons are:

• Play: run to the next breakpoint
• Step over: advance to the next line in the same function.
• Step into: advance to the next line in the function, unless on a function call, in which case enter the function being called
• Step out: run to the end of the current function

Use a source map

JavaScript sources are often combined and minified to make delivering them from the server more efficient. Increasingly, too, JavaScript running in a page is machine-generated, as when compiled from a language like CoffeeScript. By using source maps, the debugger can map the code being executed to the original source files, making debugging much, much easier.

To tell the Debugger to use source maps if they are available, click the "Debugger settings" button and select "Show original sources" from the list of settings that pops up:

Of course, for this to work, you will need to have supplied a source map for the JavaScript running in the page. Do this by appending a comment directive to your source file:

//# sourceMappingURL=https://example.com/path/to/your/sourcemap.map

Examine variables

When the code has stopped at a breakpoint, you can examine its state in the variables pane of the debugger:

Variables in global scope and in function, block, "with" scopes, etc. are listed separately, and you can expand objects to see their properties. You can also filter the variables shown using the "*" prefix in the script filter:

Modify variables

When the code has stopped at a breakpoint, you can modify variables in the variables pane of the debugger. Just click on the variable's current value and you'll be able to type there:

Watch an expression

You can watch the value of a JavaScript expression using the "Add watch expression" function in the variables pane.

Debug mobile devices

To learn how to debug mobile devices, see the guide to remote debugging.

Black box a source

In modern web development, we often rely on libraries like jQuery, Ember, or Angular, and 99% of the time we can safely assume that they “just work”. We don’t care about the internal implementation of these libraries: we treat them like a black box. However, a library’s abstraction leaks during debugging sessions when you are forced to step through its stack frames in order to reach your own code. With black boxing, you can tell the debugger to ignore the details of selected sources.

In versions of Firefox before Firefox 27, you can black box a source by clicking the eyeball icon next to the source in the source list pane:

From Firefox 27 onwards, enable or disable black boxing for a source by selecting the source in the source list pane and clicking the eyeball icon at the bottom left:

You can black box several sources at once by opening the developer toolbar and using the dbg blackbox command:

When a source is black boxed:

• Any breakpoints it may have are disabled.
• When “pause on exceptions” is enabled, the debugger won’t pause when an exception is thrown in the black boxed source; instead it will wait until (and if) the stack unwinds to a frame in a source that isn’t black boxed.
• The debugger will skip through black boxed sources when stepping.

Pretty-print a minified file

To pretty-print a file that has been minified, open the minified file and click the icon that contains a pair of braces:

The file will now appear in a more readable format:

From Firefox 29 onwards, you can instruct the debugger to detect minified sources and pretty-print them for you automatically, by selecting "Auto Prettify Minified Sources" in the Debugger settings.

Access debugging in add-ons

The following items are accessible in the context of chrome://browser/content/debugger.xul (or, in version 23 beta, chrome://browser/content/devtools/debugger.xul):

• window.addEventListener("Debugger:EditorLoaded") - called when the read-only script panel loaded.
• window.addEventListener("Debugger:EditorUnloaded")

Relevant files:

• chrome://browser/content/devtools/debugger-controller.js
• chrome://browser/content/devtools/debugger-toolbar.js
• chrome://browser/content/devtools/debugger-view.js
• chrome://browser/content/devtools/debugger-panes.js

Unfortunately there is not yet any API to evaluate watches/expressions within the debugged scope, or highlight elements on the page that are referenced as variables in the debugged scope. (currently a work in progress, see bug 653545.)

Keyboard shortcuts

1. By default, on some Macs, the function key is remapped to use a special feature: for example, to change the screen brightness or the volume. See this guide to using these keys as standard function keys. To use a remapped key as a standard function key, hold the Function key down as well (so to open the Profiler, use Shift + Function + F5).

Global shortcuts

These shortcuts work in all tools that are hosted in the toolbox.