Inconsistencies within the Debugger PlayGround documentation

[schumbar]

Issues with Debugger Documentation

I have found some issues with the "Introduction to Debugger" documentation. I will list the issues below.

Page 1: Introduction

1. The command given to open the debugger on windows is "shift + ctrl + s". This command should instead be "shift + ctrl + i".

   • Please see section A within the screenshot labeled "wrong_debugger_labels.png".
   • 

2. The picture labeled "All of the tools available in the tools pane" is mislabeled. The top two panes should be listed as the toolbar and watch expressions.

   • Please see the attached picture labeled "wrong_debugger_labels.png".
   • 

Page 2: Find the Value of a Variable

1. There is no source code provided to the user. They are unable to edit the associated JavaScript file (see error fix malformed URL in promoted Twitter tweet (workaround for #1) #2 below).
2. When trying to edit the JavaScript within the debugger, the user is unable to modify the JavaScript within the debugger. The documentation states:

If we use one of the three methods to look at the value of title, we can spot our issue. The value isn’t a string like we’d expect, but rather it is an entire object! If we hover over title and scroll through its different properties, we’ll find that we should have referenced the ‘value’ property of the object instead of the entire object itself. Fix line 14 and the app will work properly.

The documentation does not tell us how to fix the line, or provide the source files so that we can fix the function locally and test it out using Brackets or some other IDE.

Page 3: The Call Stack

1. Once again, the page mentions fixing a line within the removeSingle function. Please see below for the quote:

If we hover over index (or number), we see that it is undefined. If we hover over dataset we’ll see that there is no number property. There is only index. A typo! The line should say:

Page 4: Conditional Breakpoints

Nothing wrong was found on this page.

Page 5: Learn More

Nothing wrong was found on this page.

Thank you!

[adrianrendek]

Similar suggestion for macOS on https://mozilladevelopers.github.io/playground/debugger/.
It says that option + command + S would open the Debugger for you (if you try this, nothing happens).
The UI itself says option + command + Z (this one works and opens the Debugger window).
:) ...bad day maybe?

[bmoconnell]

Hi! I found this comment very helpful. I am a beginner in Javascript, and was finding my inability to do this debugging task disheartening. This comment let me know I couldn't do the task because editing line 14 is not possible, not because I was failing at it.