Update debug-javascript.md documentation #423
Open
+80
−63
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
mindctrl
suggested changes
Dec 3, 2025
| - **If the issue only occurs in one browser** → it may be browser‑specific (e.g., an extension conflict). | ||
| - **If the issue occurs in all browsers** → it is likely a JavaScript or plugin/theme error. | ||
|
|
||
| 👉 Note: Browser extensions (ad blockers, privacy tools) can sometimes interfere with JavaScript. Try disabling extensions or using a private/incognito window to rule this out. |
Contributor
There was a problem hiding this comment.
Is there convention for highlighting a sentence with an emoji like this in the WP documentation? I don't recall seeing one. If not, I recommend we don't start doing it here and just make the note intro bold.
Suggested change
| 👉 Note: Browser extensions (ad blockers, privacy tools) can sometimes interfere with JavaScript. Try disabling extensions or using a private/incognito window to rule this out. | |
| **Note:** Browser extensions (ad blockers, privacy tools) can sometimes interfere with JavaScript. Try disabling extensions or using a private/incognito window to rule this out. |
|
|
||
| - **Chrome / Edge / Opera**: Press **F12** (or `Ctrl+Shift+I` / `Cmd+Option+I`) → select the **Console** tab. | ||
| - **Firefox**: Press **F12** (or `Ctrl+Shift+K` / `Cmd+Option+K`) → **Console** tab. | ||
| - **Safari**: First enable the Develop menu: `Safari → Settings → Advanced → Show Develop menu`. Then open **Develop → Show JavaScript Console**. |
Contributor
There was a problem hiding this comment.
Some versions of macOS call the option "Show features for web developers" (same location).
Also once enabled, Cmd+Option+I will open the console like other browsers.
| @@ -0,0 +1,80 @@ | |||
| # Using Your Browser to Diagnose JavaScript Errors | |||
Contributor
There was a problem hiding this comment.
Was there a reason the original filename was changed for this new one?
There was a problem hiding this comment.
I think just for the sake of review - it needs to be named back to the original name
Contributor
|
@garrettb-imh are you able to follow up on this PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The “Using Your Browser to Diagnose JavaScript Errors” article is still helpful but outdated in browser instructions and links. I’ve modernized it to:
• Update DevTools access instructions (Chrome/Edge/Opera via F12, Safari/Firefox current steps).
• Add a note about browser extensions sometimes causing conflicts.
• Update support forum links to WordPress.org’s current support pages.
• Improve readability and SEO with clearer steps and headings.