mdn/content

Native Messaging add-on tutorial does not specify how to view console output.

Open

#33,315 opened on Apr 29, 2024

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Markdown (22,427 forks)batch import
Content:WebExthelp wanted

Repository metrics

Stars
 (8,900 stars)
PR merge metrics
 (Avg merge 7d 3h) (147 merged PRs in 30d)

Description

MDN URL

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging

What specific section or headline is this issue about?

No response

What information was incorrect, unhelpful, or incomplete?

Apparently, Firefox doesn't display the content.log() output of a background script in its own console. This makes testing very confusing and cumbersome for new users, who will inevitably be stuck wondering why they're not getting any output.

What did you expect to see?

I expected to see output in the Firefox console from my program.

Do you have any supporting links, references, or citations?

https://stackoverflow.com/questions/39076184/how-do-i-see-the-console-log-output-of-a-background-script-in-a-firefox-webexten

The answer to this question is incorrect, as the "Show Content Messages" option appears to have been removed from the gear icon in the Firefox console.

Do you have anything more you want to share?

We should either specify that displaying the contents of console.log() requires an add-on or specify how to enable it in Firefox.

MDN metadata

Contributor guide

Research direction
Verify the current method to view console.log output from background scripts in Firefox (e.g., using about:debugging or browser console filters) and update the Native messaging documentation to include this information.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90