1381261 - Browser console shows the Javascript error messages from a content script, but the Developer Tools console does not.

Status: RESOLVED DUPLICATE of bug 1410932

(WebExtensions :: Developer Tools, defect, P3)

Description

[John Nagle]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170612122310

Steps to reproduce:

Developing an add-on using WebExtensions. Ran a content script with

    "use strict"
   ...
    console.log("Load start.");
    foofoofoo; // ***TEMP*** force error




Actual results:

Developer console for the appropriate tab shows the logged "Load start.", but no error message appears for the Javascript error, even though they're coming from the same Javascript execution. 

The error message does appear in the browser console (CTL-SHIFT-J).



Expected results:

Either the developer console should show content script errors, or it should be documented that it doesn't. 

Current WebExtensions documentation tells developers to use the developer console, and the browser console (formerly the error console) is  deprecated. See "Debugging content scripts" at "https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Debugging", which makes no mention of the need to use the Browser Console.

Comment 1

[Andy McKay]

Is there a bug already on this Luca?

Comment 2

[Luca Greco [:rpl] [:luca] [:lgreco]]

Not specifically related to the errors coming from the content scripts (which should be listed in the tab developer tools console),
there is Bug 1006102 but it is more about filtering out the non-extension errors, e.g. errors from other Firefox internals, from the addon debugging window's developer tools console).