Added net logging to DownloadItem.

chrome/browser/resources/net_internals/source_entry.js

Index: chrome/browser/resources/net_internals/source_entry.js
diff --git a/chrome/browser/resources/net_internals/source_entry.js b/chrome/browser/resources/net_internals/source_entry.js
index 7476f647bbd25885a89a0d498e0fea3321e59753..0cb526e203726d2c7a5929a1d28c452e90878a0d 100644
--- a/chrome/browser/resources/net_internals/source_entry.js
+++ b/chrome/browser/resources/net_internals/source_entry.js
@@ -140,6 +140,9 @@ var SourceEntry = (function() {
             case LogEventType.DOWNLOAD_FILE_OPENED:
               this.description_ = e.params.file_name;
               break;
+            case LogEventType.DOWNLOAD_ITEM_ACTIVE:
+              this.description_ = e.params.intermediate_name;
+              break;
           }
           break;
         case LogSourceType.FILESTREAM:
@@ -183,6 +186,10 @@ var SourceEntry = (function() {
         e = this.findLogEntryByType_(LogEventType.DOWNLOAD_FILE_OPENED);
         if (e != undefined)
           return e;
+        // History items are never opened, so use the activation info
+        e = this.findLogEntryByType_(LogEventType.DOWNLOAD_ITEM_ACTIVE);

[Randy Smith (Not in Mondays), 2012/02/03 18:23:37]

Why aren't we using the DOWNLOAD_ITEM_ACTIVE in preference to the
DOWNLOAD_FILE_OPENED?  I think it's likely to happen earlier; is there some
reason to prefer file opening?

[ahendrickson, 2012/02/04 05:24:04]

This information is used to determine what to show for a description of the
event source.  The ACTIVE event doesn't have the right information for a new
download, but does for the one loaded from the history DB.

+        if (e != undefined)
+          return e;
       }
       if (this.entries_.length >= 2) {
         if (this.entries_[0].type == LogEventType.REQUEST_ALIVE ||