Road
May 9, 2025, 2:23pm
1
Tell us what’s happening:
Question 3 states “Which tab do Chrome and Firefox browsers switch to when they encounter the debugger statement?”
This is not discussed anywhere on the page or in the video.
(Just to confirm, I’m not asking for the answer to this question to be provided in a reply to this forum post, I just want to bring this to the attention of the freeCodeCamp devs.)
Your browser information:
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36
Challenge Information:
Debugging Techniques - How Does the Debugger Statement Work?
ILM
May 9, 2025, 2:32pm
2
would you be up to opening a github issue for this?
1 Like
The answer is also wrong. I opened an issue for it.
opened 05:19PM - 09 May 25 UTC
scope: curriculum
status: waiting triage
full stack cert
### Describe the Issue
1. The answer to the last question is not correct. Firef… ox switches to the Debugger tab, not the Network tab (I guess technically, it switches to the Sources sub tab on the main Debugger tab).

Also, it is the "Sources" tab, not "Source" tab in Chrome.
https://github.com/freeCodeCamp/freeCodeCamp/blob/01722e62a75197509824d829e4b2c61ece12b6b3/curriculum/challenges/english/25-front-end-development/lecture-debugging-techniques/6733becf4b0c353553b9bfa4.md?plain=1#L161
Apparently the answer to this question has also not been taught?
https://forum.freecodecamp.org/t/debugging-techniques-how-does-the-debugger-statement-work/746579
---
2. Pretty sure, the "They keep reloading the page" part of the "They keep reloading the page and allow you to resume by clicking a play button." answer is wrong. Also, the lecture is ambiguous in what it says, and in my opinion incorrect in its assertion.
Transcript:
> In addition, when you use the debugger statement, modern browsers will pause code execution at the specified line. They also allow you to resume execution by clicking the play button, **but the page itself does not automatically reload unless manually triggered.**
But then later it says:
> If you reload the page with the console opened, **you'll see that the page keeps reloading**, confirming that the execution of the code is only paused, not stopped. If you want the execution to continue, you can click the play button.
I do not believe the statement "you'll see that the page keeps reloading" is correct, technically what I believe is happening is this:
*If* the `debugger` statement is placed in the top-level of the script code, execution is paused _before_ the page has finished loading. So it gets "stuck" in the page loading state. It is not _reloading_ the page. Also, if the `debugger` statement is inside a function call that is invoked _after_ the page is done loading, this is not the case at all, and the page is not "stuck" in a loading state.
Not sure how best to rephrase what is meant by "the page keeps reloading" but it isn't correct in my opinion. Any correction to this will need to be in the video and the quiz answer.
https://github.com/freeCodeCamp/freeCodeCamp/blob/01722e62a75197509824d829e4b2c61ece12b6b3/curriculum/challenges/english/25-front-end-development/lecture-debugging-techniques/6733becf4b0c353553b9bfa4.md?plain=1#L117
### Affected Page
https://www.freecodecamp.org/learn/full-stack-developer/lecture-debugging-techniques/how-does-the-debugger-statement-work
### Your code
```
```
### Expected behavior
1. Correct the answer to the third question.
2. Rephrase what is meant by "the page keeps reloading" to make it more correct.
### Screenshots
_No response_
### System
- Device: [e.g. iPhone 6, Laptop]
- OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
- Browser: [e.g. Chrome, Safari]
- Version: [e.g. 22]
### Additional context
_No response_
1 Like