Closed
Bug 1072687
Opened 10 years ago
Closed 2 years ago
Log.jsm ConsoleAppender should use Console.jsm to provide rich messages (e.g. inspectable objects)
Categories
(Toolkit :: General, enhancement)
Toolkit
General
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: MattN, Unassigned)
References
Details
There isn't currently a good way to use the ConsoleAppender and not have objects/array/etc. stringified on the way to the console. One of the advantages of the Browser Console for logging is you can inspect objects/arrays by clicking on them.
Flags: firefox-backlog?
Reporter | ||
Comment 1•10 years ago
|
||
Note that care should be taken to preserve the filename and line numbers of where the caller to Log.jsm was instead of always showing the console logging coming from Log.jsm.
Updated•10 years ago
|
Flags: firefox-backlog? → firefox-backlog+
Updated•10 years ago
|
Flags: qe-verify?
Updated•2 years ago
|
Severity: normal → S3
Comment 3•2 years ago
|
||
I'm going to wontfix this as we are aiming to remove Log.sys.mjs (bug 1828156) and Console.sys.mjs (bug 1430810).
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•