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

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

 /*
  * Copyright (C) 2007, 2008 Apple Inc.  All rights reserved.
  * Copyright (C) 2009 Joseph Pecoraro
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions
  * are met:
  *
  * 1.  Redistributions of source code must retain the above copyright
  *     notice, this list of conditions and the following disclaimer.
@@ skipping 639 matching lines @@
         function writeNextChunk(stream, error)
         {
             if (messageIndex >= this.itemCount() || error) {
                 stream.close();
                 progressIndicator.done();
                 return;
             }
             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));
             progressIndicator.setWorked(messageIndex);
         }
 
     },
 
     /**
      * @param {!WebInspector.ConsoleViewMessage} lastMessage
@@ skipping 741 matching lines @@
             return true;
         }
         return false;
     }
 }
 
 /**
 * @typedef {{messageIndex: number, matchIndex: number}}
 */
 WebInspector.ConsoleView.RegexMatchRange;