docs: fix broken link in Readme pointing to enable remote debugging docs #393
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
The old URL just loads a white page and I also don't know why that should be documented on a page for "Firefox profiler". This was a hard search to find that though, because for some reason the official docs name it "browser's toolbox" (searching for "enable remote debugging" was less fitting then), probably, because debugging a WebExtension is just a side-effect, so yeah… I can see how that comes from. It's way [easier to find that low level stuff like the protocol](https://firefox-source-docs.mozilla.org/devtools/backend/protocol.html). 😅 And unfortunately [the nice WebExtensionWorkshop](https://extensionworkshop.com/documentation/develop/debugging/) page, which is also from Mozilla, also does not offer any information on that topic, just in-browser debugging.
rugk
added a commit
to rugk/extension-workshop
that referenced
this pull request
Aug 19, 2025
…debug In firefox-devtools/vscode-firefox-debug#393 I've found out, that the possibility of debugging extensions using an external program is not even mentioned at all here. I guess at least such a minimal version like this would be useful. The way how to do it is then documented there.
|
Ah the extension seems to use port 8000 when not configured otherwise, my Firefox uses 6000. Maybe also add Actually though, even though Then I just configured it to use the server port. I am confused? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 old URL just loads a white page and I also don't know why that should be documented on a page for "Firefox profiler".
This was a hard search to find that though, because for some reason the official docs name it "browser's toolbox" (searching for "enable remote debugging" was less fitting then), probably, because debugging a WebExtension is just a side-effect, so yeah… I can see how that comes from.
It's way easier to find that low level stuff like the protocol. 😅
And unfortunately the nice WebExtensionWorkshop page, which is also from Mozilla, also does not offer any information on that topic, just in-browser debugging.