Export all data from Web Console




Developer Tools: Console
7 years ago
8 days ago


(Reporter: rc, Unassigned, Mentored)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [console][parity-chrome])



7 years ago
Currently, the only way to export data from the web console is to select all and copy the lines to the clipboard for pasting into an external editor. We should provide an export mechanism that saves all lines from the console and any headers and responses (bodies if checked) in the file.


5 years ago
Component: Developer Tools → Developer Tools: Console


5 years ago
Priority: -- → P3

Comment 1

3 years ago
The recent addition of persistent console log history makes this option more desirable to me: as the console takes over more of my development time I find myself wanting to be able to export a complex history more and more. This has shown its worth in Python's `readline.write_history_file` as well.
Duplicate of this bug: 1157200
Note that there was an extension for Firebug called ConsoleExport[1], which offered this feature. Also the Chrome DevTools have an export option for quite some time[2].


[1] https://github.com/firebug/consoleexport
[2] https://twitter.com/addyosmani/status/590646206491156482
This sounds interesting. 
What chrome seems to do is to output every message in a file, with the location first, separated by a line break. i.e. :

script-a.js mylog from script-a
script-b.js mylog from script-b

I guess we could build this upon our "Copy message" context menu entry.
The action item could be in the context menu entry as well as in the future Console settings panel.

As a first step, we could do this strictly as "Copy message" works, and then take care of putting the location at the beginning of the message in a follow-up.

If anyone wants to work on this, I would gladly mentor them.
Mentor: nchevobbe@mozilla.com
"Copy (Message)" from the context menu is not expanding logged objects which are represented by {…}.
These should (at least optionally) be expanded recursively for such an export.

This is really limiting the possibility to send web application developers your log output when seeing a problem happen...
Whiteboard: [console] → [console][parity-chrome]
You need to log in before you can comment on or make changes to this bug.