Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Enabled by default visibility of extension pages and content scripts logs in the BrowserConsole #1725

Merged
merged 2 commits into from
Oct 17, 2019

Conversation

rbrishabh
Copy link
Contributor

Fixes #1702

Hey @rpl!

I hope you're doing well!

I believe this is the only change that is needed to fix this issue. Is that right?

Also, do I need to use a conditional statement to only set extensions.logging.enabled to true when --browser-console is sent as a parameter when running web-ext?

Thanks!

@coveralls
Copy link

coveralls commented Oct 5, 2019

Coverage Status

Coverage remained the same at 100.0% when pulling c96a0dc on rbrishabh:issue-console into 5be19b0 on mozilla:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 23a2aec on rbrishabh:issue-console into 5be19b0 on mozilla:master.

src/firefox/preferences.js Outdated Show resolved Hide resolved
@rbrishabh
Copy link
Contributor Author

Ahh! Since I didn't find devtools.browserconsole.contentMessages, I assumed I was supposed to look for something similar for logging considering the issue summary of #1702 as just a pointer to the kind of change you might want to make.

Anyways, I made the change in preferences.js now.

Please review this again and let me know what you think.
Thanks!

@rpl

@rbrishabh rbrishabh requested a review from rpl October 8, 2019 02:52
@rbrishabh
Copy link
Contributor Author

Hey @rpl, could you find any time to look into this?

Thanks!

@rpl
Copy link
Member

rpl commented Oct 17, 2019

@rbrishabh Thanks, it looks good and works as expected.

Also, do I need to use a conditional statement to only set extensions.logging.enabled to true when --browser-console is sent as a parameter when running web-ext?

I wouldn't bother to "only enabling it when --browser-console option is also passed to web-ext run", as an extension developer I would prefer it to be enabled by default to ensure that if I open the Browser Console manually (without using the --browser-console option) I'm still going to see the extension logs without having to find out the option and enabled it manually (the option can be toggle from the gear icon in the top-right corner of the Browser Console, but I think that it is quite easy to miss to notice it).

If we experience issues related to that preference we may re-evaluate this choice in a separate follow up.

In the meantime, thanks for the PR! I'm going to merge right now \o/

@rpl rpl changed the title fix: enable extensions logging in browser's console feat: Enabled by default visibility of extension pages and content scripts logs in the BrowserConsole Oct 17, 2019
@rpl rpl merged commit b34d9c8 into mozilla:master Oct 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable "devtools.browserconsole.contentMessages" before running Firefox
3 participants