DevTools: include traces when exporting console log via 'Save as'

third_party/WebKit/Source/devtools/front_end/console/ConsoleView.js

Index: third_party/WebKit/Source/devtools/front_end/console/ConsoleView.js
diff --git a/third_party/WebKit/Source/devtools/front_end/console/ConsoleView.js b/third_party/WebKit/Source/devtools/front_end/console/ConsoleView.js
index 1a77e9750f7711779fb9fda5e39656600c8e6b52..c06abaec5dafec3ccc861ebf3a5764cc90df4687 100644
--- a/third_party/WebKit/Source/devtools/front_end/console/ConsoleView.js
+++ b/third_party/WebKit/Source/devtools/front_end/console/ConsoleView.js
@@ -657,7 +657,7 @@ WebInspector.ConsoleView.prototype = {
             var lines = [];
             for (var i = 0; i < chunkSize && i + messageIndex < this.itemCount(); ++i) {
                 var message = this.itemElement(messageIndex + i);
-                lines.push(message.searchableElement().deepTextContent());

[dgozman, 2016/08/24 18:58:00]

Do we need searchableElement anymore? Shouldn't search work on the same data as
export?

[luoe, 2016/08/24 20:31:01]

The only reason I can think might be users who don't want to search the anchor
location (source file:line).

+                lines.push(message.formattedMessage().deepTextContent());
             }
             messageIndex += i;
             stream.write(lines.join("\n") + "\n", writeNextChunk.bind(this));