Script Panel

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
(Moved Breakpoints Side Panel description into its own page)
m (Adjusted shortcuts for the new style)
(10 intermediate revisions not shown)
Line 3: Line 3:
== Options Menu ==
== Options Menu ==
 +
This menu is reachable via the little arrow in the panel tab ( [[Image:ScriptPanelOptionsMenuArrow.png]] ) or by right-clicking on on the panel tab (since [[Firebug Release Notes#Firebug 1.9|Firebug 1.9]]).
 +
{| class="wikitable" style="width:100%; vertical-align:top;"
{| class="wikitable" style="width:100%; vertical-align:top;"
|- bgcolor=lightgrey
|- bgcolor=lightgrey
Line 10: Line 12:
|-  
|-  
| Show chrome sources || <code>extensions.firebug.service.showAllSourceFiles</code> || Toggles the display of program and add-on internal sources.
| Show chrome sources || <code>extensions.firebug.service.showAllSourceFiles</code> || Toggles the display of program and add-on internal sources.
-
Note that Firebug will still not activate for chrome URLs unless you also set <code>service.filterSystemURLs</code> to false (see [[Firebug_Preferences]]).
+
Note that Firebug will still not activate for chrome URLs unless you also set <code>service.filterSystemURLs</code> to false (see [[Firebug Preferences]]).
|-  
|-  
| Track Throw/Catch || <code>extensions.firebug.service.trackThrowCatch</code> || Toggles tracking of throw/catch blocks
| Track Throw/Catch || <code>extensions.firebug.service.trackThrowCatch</code> || Toggles tracking of throw/catch blocks
Line 21: Line 23:
== Panel Toolbar ==
== Panel Toolbar ==
=== Break On Next ===
=== Break On Next ===
-
The "Break On Next" button gives you the possiblity to stop the script at the next executed command. This can be a user action, a timeout or anything else that causes script execution. As soon as you click on the button, it is armed. When any script execution occurs now, the debugger will halt the script and you can step through it.
+
The ''Break On Next'' button ( [[File:Break_On_Next_Button.png]] ) gives you the possiblity to stop the script at the next executed command. This can be a user action, a timeout or anything else that causes script execution. As soon as you click on the button, it is armed. When any script execution occurs now, the debugger will halt the script and you can step through it.
 +
 
 +
There are several other [[Break On ...]] features available at the other panels.
=== Script Type Menu ===
=== Script Type Menu ===
Line 46: Line 50:
{| class="wikitable" style="vertical-align:top;"
{| class="wikitable" style="vertical-align:top;"
|- bgcolor=lightgrey
|- bgcolor=lightgrey
-
! style="width:60px" | Type || style="width:50px" | Button || style="width:70px" | Shortcut || Description
+
! style="width:60px" | Type || style="width:50px" | Button || style="width:100px" | Shortcut || Description
|-  
|-  
-
| Rerun || [[Image:rerunButton.png|center]] || - || Reruns the current call stack (see [http://www.softwareishard.com/blog/planet-mozilla/firebug-tip-re-run-this-stack/ Honza's blog post] for more info)
+
| Rerun || [[Image:rerunButton.png|center]] || <code class="key">Shift</code> + <code class="key">F8</code> || Reruns the current call stack (see [http://www.softwareishard.com/blog/planet-mozilla/firebug-tip-re-run-this-stack/ Honza's blog post] for more info)
|-  
|-  
-
| Continue || [[Image:continueButton.png|center]] || F8 || Continues script execution until the next breakpoint or the execution ends
+
| Continue || [[Image:continueButton.png|center]] || <code class="key">F8</code> || Continues script execution until the next breakpoint or the execution ends
|-  
|-  
-
| Step Into || [[Image:stepIntoButton.png|center]] || F11 || Jumps into the body of executed functions, so you can debug them
+
| Step Into || [[Image:stepIntoButton.png|center]] || <code class="key">F11</code> || Jumps into the body of executed functions, so you can debug them
|-
|-
-
| Step over || [[Image:stepOverButton.png|center]] || F10 || Executes functions, but doesn't jump into them, instead moves to the next line of the same scope
+
| Step over || [[Image:stepOverButton.png|center]] || <code class="key">F10</code> || Executes functions, but doesn't jump into them, instead moves to the next line of the same scope
|-
|-
-
| Step out || [[Image:stepOutButton.png|center]] || Shift + F11 || Executes the rest of the current function and jumps back to it's caller
+
| Step out || [[Image:stepOutButton.png|center]] || <code class="key">Shift</code> + <code class="key">F11</code> || Executes the rest of the current function and jumps back to it's caller
|}
|}
 +
 +
<em>test</em>
== Breakpoints ==
== Breakpoints ==
Breakpoints in Firebug are used to debug JavaScript code. They will stop script execution at a specific point and give you control over script execution.
Breakpoints in Firebug are used to debug JavaScript code. They will stop script execution at a specific point and give you control over script execution.
 +
 +
==== Setting breakpoints ====
 +
The Breakpoint Column allows you to set breakpoints. By clicking on it a breakpoint is set for the line. Clicking it again removes the breakpoint again.
=== Types ===
=== Types ===
You can set breakpoints to stop script execution as soon as it reaches them for debugging purposes. Currently you can manually create five different types of breakpoints:
You can set breakpoints to stop script execution as soon as it reaches them for debugging purposes. Currently you can manually create five different types of breakpoints:
 +
{| class="wikitable" style="vertical-align:top;"
{| class="wikitable" style="vertical-align:top;"
|- bgcolor=lightgrey
|- bgcolor=lightgrey
! style="width:130px" | Type || style="width:100px" | Panel || Description
! style="width:130px" | Type || style="width:100px" | Panel || Description
|-  
|-  
-
|Script Breakpoints || Script Panel || Standard type of breakpoints
+
| Script Breakpoints || Script Panel || Standard type of breakpoints
|-  
|-  
-
|Error Breakpoints || [[Console Panel]] || Trigger on a specific JavaScript error
+
| Error Breakpoints || [[Console Panel]] || Trigger on a specific JavaScript error
|-
|-
-
|HTML Breakpoints || [[HTML Panel]] || Trigger on HTML manipulation
+
| HTML Breakpoints || [[HTML Panel]] || Trigger on HTML manipulation
|-
|-
-
|DOM Breakpoints || [[DOM Panel]] || Trigger on DOM property manipulation
+
| DOM Breakpoints || [[DOM Panel]] || Trigger on DOM property manipulation
|-
|-
-
|XHR Breakpoints || [[Net Panel]] || Trigger on XMLHttpRequests
+
| XHR Breakpoints || [[Net Panel]] || Trigger on XMLHttpRequests
 +
|-
 +
| Cookie Breakpoints || [[Cookies Panel]] || Trigger on cookie manipulation
|}
|}
=== Conditions ===
=== Conditions ===
-
For manually set breakpoints you also have the possibility to set conditions, at which they trigger. These conditions can be very complex, but most of the time you'll want to limit breaking to specific variable values.
+
For manually set breakpoints you also have the possibility to set conditions, at which they trigger. Doing so opens the Breakpoint Condition Editor:
 +
 
 +
[[File:ScriptBreakpointConditionEditor.png]]
 +
 
 +
These conditions can be very complex, but most of the time you'll want to limit breaking to specific variable values.
An example for this could be having a counter and you want to stop execution when the counter reaches a specific value. Another situation would be to stop execution when a specific variable is defined resp. undefined.
An example for this could be having a counter and you want to stop execution when the counter reaches a specific value. Another situation would be to stop execution when a specific variable is defined resp. undefined.
=== Automatic Breakpoints ===
=== Automatic Breakpoints ===
-
Furthermore the script execution can be stopped via the different implemented [[Break On...]] features of each panel, which doesn't require explicitly setting of breakpoints.
+
Furthermore the script execution can be stopped via the different implemented [[Break On ...]] features of each panel, which doesn't require explicitly setting of breakpoints.
== Variable Tooltips ==
== Variable Tooltips ==
Line 107: Line 123:
== See also ==
== See also ==
-
[[Jsd]] (JavaScript interface for debugging Javascript)
+
* [[Script Debugging]]
 +
* [[Jsd]] (JavaScript interface for debugging Javascript)

Revision as of 08:15, 21 May 2013

Script Panel

The main purpose of the script panel is to debug JavaScript code. Therefore the script panel integrates a powerful debugging tool based on features like different kinds of breakpoints, step-by-step execution of scripts, a display for the variable stack, watch expressions and more.

Contents

Options Menu

This menu is reachable via the little arrow in the panel tab ( ScriptPanelOptionsMenuArrow.png ) or by right-clicking on on the panel tab (since Firebug 1.9).

Option Preference Description
Enabled/Disabled extensions.firebug.script.enableSites Enables the Script Panel
Show chrome sources extensions.firebug.service.showAllSourceFiles Toggles the display of program and add-on internal sources.

Note that Firebug will still not activate for chrome URLs unless you also set service.filterSystemURLs to false (see Firebug Preferences).

Track Throw/Catch extensions.firebug.service.trackThrowCatch Toggles tracking of throw/catch blocks
Show Break Notifications extensions.firebug.showBreakNotification Toggles the display of break notifications

For more info about tweaks available in Firebug please see the full list of preferences.

Panel Toolbar

Break On Next

The Break On Next button ( Break On Next Button.png ) gives you the possiblity to stop the script at the next executed command. This can be a user action, a timeout or anything else that causes script execution. As soon as you click on the button, it is armed. When any script execution occurs now, the debugger will halt the script and you can step through it.

There are several other Break On ... features available at the other panels.

Script Type Menu

The Script Type Menu filters the Script Location Menu by different types of scripts. Thereby three different kinds of scripts are distinguished:

Type Description
static All scripts, that are loaded together with the page (via the <script> tag)
eval() Scripts, that are executed using the eval() function (typically scripts loaded via an XMLHttpRequest)
event Scripts, that are generated through an event (like e. g. client side table sorting)

You have the option to just show static scripts, static + eval scripts, static + event script or all types of scripts.

Script Location Menu

All scripts filtered by the type(s) selected in the Script Type Menu will be shown inside this menu. Any characters you type on the keyboard while the list of files is open will filter the list to make it easier to find files. By selecting one of the scripts it will be shown inside the Main Panel.

If you right-click on the file list, you'll get options for opening the script in a separate browser tab, copying its location to the clipboard, or opening it inside the DOM Panel.

Execution Control Buttons

The execution buttons are enabled as soon as the debugger is stopped. There are four buttons, which can be used for debugging:

Type Button Shortcut Description
Rerun
RerunButton.png
Shift + F8 Reruns the current call stack (see Honza's blog post for more info)
Continue
ContinueButton.png
F8 Continues script execution until the next breakpoint or the execution ends
Step Into
StepIntoButton.png
F11 Jumps into the body of executed functions, so you can debug them
Step over
StepOverButton.png
F10 Executes functions, but doesn't jump into them, instead moves to the next line of the same scope
Step out
StepOutButton.png
Shift + F11 Executes the rest of the current function and jumps back to it's caller

test

Breakpoints

Breakpoints in Firebug are used to debug JavaScript code. They will stop script execution at a specific point and give you control over script execution.

Setting breakpoints

The Breakpoint Column allows you to set breakpoints. By clicking on it a breakpoint is set for the line. Clicking it again removes the breakpoint again.

Types

You can set breakpoints to stop script execution as soon as it reaches them for debugging purposes. Currently you can manually create five different types of breakpoints:

Type Panel Description
Script Breakpoints Script Panel Standard type of breakpoints
Error Breakpoints Console Panel Trigger on a specific JavaScript error
HTML Breakpoints HTML Panel Trigger on HTML manipulation
DOM Breakpoints DOM Panel Trigger on DOM property manipulation
XHR Breakpoints Net Panel Trigger on XMLHttpRequests
Cookie Breakpoints Cookies Panel Trigger on cookie manipulation

Conditions

For manually set breakpoints you also have the possibility to set conditions, at which they trigger. Doing so opens the Breakpoint Condition Editor:

ScriptBreakpointConditionEditor.png

These conditions can be very complex, but most of the time you'll want to limit breaking to specific variable values. An example for this could be having a counter and you want to stop execution when the counter reaches a specific value. Another situation would be to stop execution when a specific variable is defined resp. undefined.

Automatic Breakpoints

Furthermore the script execution can be stopped via the different implemented Break On ... features of each panel, which doesn't require explicitly setting of breakpoints.

Variable Tooltips

When the debugger halted the script, you are able to get information about the script variables by hovering them. A popup will appear showing the current value of the hovered variable.

Side Panels

The Side Panels of the Script Panel offer different useful information and functionality about the executed scripts.

Watch

The Watch Side Panel offers the possibility to enter watch expressions allowing to follow changes of variable values while debugging.

Stack

The Stack Side Panel contains information about the call stack trace for the currently debugged function.

Breakpoints

The Breakpoints Side Panel lists the defined breakpoints and gives the possibility to toggle their activation plus additional options for changing the behavior of the breakpoints.

Search

The text input box in the upper right corner searches the source code. When you click in to the box, an auxiliary panel allows you to pick search direction, single or multiple files, and case sensitivity. The text has special case code to support:

  • Go to Line: The symbol # followed by a number will incrementally move the line number,
  • Case by Case: If the case sensitivity setting is not used, then an all lower case word will mean case-insensitive search, but a mixedCase word will cause case sensitive matches.

See also

Personal tools