You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 1-js/03-code-quality/01-debugging-chrome/article.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ For example, here `1+2` results in `3`, and `hello("debugger")` returns nothing,
46
46
47
47
## Breakpoints
48
48
49
-
Let's examine what's going on within the code of the [example page](debugging/index.html). In `hello.js`, click at the line number `4`. Yes, right on the `"4"` digit, not on the code.
49
+
Let's examine what's going on within the code of the [example page](debugging/index.html). In `hello.js`, click at line number `4`. Yes, right on the `4` digit, not on the code.
50
50
51
51
Congratulations! You've set a breakpoint. Please also click on the number for line `8`.
52
52
@@ -123,7 +123,7 @@ Now it's time to *trace* the script.
123
123
There are buttons for it at the top of the right pane. Let's engage them.
124
124
125
125
<spanclass="devtools"style="background-position:-7px-76px"></span> -- continue the execution, hotkey `key:F8`.
126
-
: Resumes the execution. If there are no additional breakpoints, then the execution just continues and the debugger looses the control.
126
+
: Resumes the execution. If there are no additional breakpoints, then the execution just continues and the debugger loses control.
127
127
128
128
Here's what we can see after a click on it:
129
129
@@ -178,7 +178,7 @@ As we can see, there are three main ways to pause a script:
178
178
179
179
Then we can examine variables and step on to see where the execution goes wrong.
180
180
181
-
There are many more options in developer tools than covered here. The full manual is at <https://developers.google.com/web/tools/chrome-devtools>
181
+
There are many more options in developer tools than covered here. The full manual is at <https://developers.google.com/web/tools/chrome-devtools>.
182
182
183
183
The information from this chapter is enough to begin debugging, but later, especially if you do a lot of browser stuff, please go there and look through more advanced capabilities of developer tools.
0 commit comments