Closed
Bug 1393026
Opened 7 years ago
Closed 7 years ago
console.log/dir results is strange for function
Categories
(WebExtensions :: Developer Tools, defect, P3)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1327280
People
(Reporter: yfdyh000, Unassigned)
References
Details
Attachments
(1 file)
544 bytes,
application/x-zip-compressed
|
Details |
console.log(() => { }) // <unavailable> background.js:1
// function () Scratchpad/1:10:1
console.dir([1, 2], () => { },[3]) // [1, 2] background.js:4, also occur in other places and Chrome.
console.log([1, 2],[3]) //Array [ 1, 2 ] Array [ 3 ]
Component: WebExtensions: Untriaged → JavaScript Engine
Product: Toolkit → Core
console.log(() => { }) // <unavailable> background.js:1
is bug 1393166, can viewed in Add-on Debugger.
Updated•7 years ago
|
Component: JavaScript Engine → WebExtensions: Developer Tools
Product: Core → Toolkit
Updated•7 years ago
|
Flags: needinfo?(lgreco)
Priority: -- → P3
Comment 2•7 years ago
|
||
The output of console.dir and console.log is different in the browser console (and partially also in the WebExtension Addon Debugging window) for two reasons:
- Bug 1327280 ([e10s] Browser console doesn't display objects from content processes (displays <unavailable>)), is the reason for the "<unavailble>" in the Browser Console when the extension is running in the extension process (currently only on Windows the webextensions are going to run in the extension process by default)
- Bug 1362023 (Enable new console in browser console) and Bug 1347127 (Enable new console frontend in Browser Toolbox) are likely to be the reason for the different output of console.dir
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•