Isolate initiation counts for downloads to their own histograms and improve

chrome/browser/download/download_throttling_resource_handler.cc

Index: chrome/browser/download/download_throttling_resource_handler.cc
diff --git a/chrome/browser/download/download_throttling_resource_handler.cc b/chrome/browser/download/download_throttling_resource_handler.cc
index 85bc6e19cbaf39fb247f93d8ee8c385c4db1b183..b61f1a5c93cea7cbdebb8cf7bc8a9235c5b9cc88 100644
--- a/chrome/browser/download/download_throttling_resource_handler.cc
+++ b/chrome/browser/download/download_throttling_resource_handler.cc
@@ -134,16 +134,16 @@ void DownloadThrottlingResourceHandler::OnRequestClosed() {
 }
 
 void DownloadThrottlingResourceHandler::ContinueDownload(bool allow) {
-  download_util::RecordDownloadCount(
-        download_util::INITIATED_BY_NAVIGATION_COUNT);
   if (request_closed_)
     return;
 
   request_allowed_ = allow;
   if (allow) {
     // And let the request continue.
+    download_util::RecordDownloadSource(download_util::INITIATED_BY_NAVIGATION);
     host_->PauseRequest(render_process_host_id_, request_id_, false);
   } else {
+    download_util::RecordDownloadSource(download_util::BLOCKED_BY_THROTTLING);

[cbentzel, 2012/02/07 18:29:32]

I don't like having this as a separate source, as the source is ultimately the
same (navigation). Prefer to have a separate histogram for the throttling
behavior. 

[Randy Smith (Not in Mondays), 2012/02/07 19:28:14]

Moved into a "Counts" histogram at the chrome layer parallel to the same
histogram in content.

     host_->CancelRequest(render_process_host_id_, request_id_, false);
   }
 }