Commit 2277f2f

committed

images

1 parent 63dc4cd commit 2277f2fCopy full SHA for 2277f2f

File tree

+445

-82

lines changed

+445

-82

lines changed

-43.1 KB

Binary file not shown.

Lines changed: 48 additions & 0 deletions

Lines changed: 101 additions & 0 deletions

Lines changed: 3 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -50,7 +50,7 @@ Congratulations! You've set a breakpoint. Please also click on the number for li`
`50`	`50`
`51`	`51`	`It should look like this (blue is where you should click):`
`52`	`52`
`53`		`-![](chrome-sources-breakpoint.png)`
	`53`	`+![](chrome-sources-breakpoint.svg)`
`54`	`54`
`55`	`55`	`A breakpoint is a point of code where the debugger will automatically pause the JavaScript execution.`
`56`	`56`
@@ -93,7 +93,7 @@ In our example, `hello()` is called during the page load, so the easiest way to
`93`	`93`
`94`	`94`	`As the breakpoint is set, the execution pauses at the 4th line:`
`95`	`95`
`96`		`-![](chrome-sources-debugger-pause.png)`
	`96`	`+![](chrome-sources-debugger-pause.svg)`
`97`	`97`
`98`	`98`	`Please open the informational dropdowns to the right (labeled with arrows). They allow you to examine the current code state:`
`99`	`99`
`@@ -125,7 +125,7 @@ There are buttons for it at the top of the right pane. Let's engage them.`
`125`	`125`
`126`	`126`	`Here's what we can see after a click on it:`
`127`	`127`
`128`		`- ![](chrome-sources-debugger-trace-1.png)`
	`128`	`+ ![](chrome-sources-debugger-trace-1.svg)`
`129`	`129`
`130`	`130`	The execution has resumed, reached another breakpoint inside `say()` and paused there. Take a look at the "Call stack" at the right. It has increased by one more call. We're inside `say()` now.
`131`	`131`