When debugging a web extension via about:debugging, the console also logs messages that are unrelated to the add-on. E.g. I loaded the MDN example extension "borderify", then clicked the "Debug" button in about:debugging. The opening Browser Toolbox listed the following errors: Content Security Policy: Directive ‘frame-src’ has been deprecated. Please use directive ‘child-src’ instead. (unknown) Key event not available on some keyboard layouts: key=“r” modifiers=“accel,alt” id=“key_toggleReaderMode” browser.xul Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xul As a user, I'd only expect to see the messages related to my extension to be logged. Sebastian  https://github.com/mdn/webextensions-examples/tree/master/borderify
Summary: When debugging an add-on console lists unrelated messages → When debugging an add-on console lists unrelated error messages
Hi Sebastian, I'm duping this issue with Bug 1006102: This issue is actually related to the error messages (the console API messages are already filtered based on the extension that the addon debugger window is targeting, which has been introduced by Bug 1211665), and Bug 1006102 has patches attached with a proposed approach (briefly described in Bug 1006102 Comment 34).
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1006102
Great! Thank you for the info, Luca! And for already working on this! :-) Just for reference, I reported that issue, because it was mentioned on Stack Overflow: https://stackoverflow.com/questions/44507730/installation-error-this-add-on-cannot-be-installed-because-it-appears-to-be-co/44515103#comment76025554_44515103 Sebastian
You need to log in before you can comment on or make changes to this bug.