Update download page to deal with new DANGEROUS_CONTENT state.

chrome/browser/resources/downloads.js

Index: chrome/browser/resources/downloads.js
diff --git a/chrome/browser/resources/downloads.js b/chrome/browser/resources/downloads.js
index ec8148d73190174dd9edaba75b849c0de17d34f1..5b02a0f1ddf8ceb3d668c32323d11417e6a313a5 100644
--- a/chrome/browser/resources/downloads.js
+++ b/chrome/browser/resources/downloads.js
@@ -305,6 +305,7 @@ Download.DangerType = {
   NOT_DANGEROUS: "NOT_DANGEROUS",
   DANGEROUS_FILE: "DANGEROUS_FILE",
   DANGEROUS_URL: "DANGEROUS_URL",
+  DANGEROUS_CONTENT: "DANGEROUS_CONTENT"

[Randy Smith (Not in Mondays), 2011/11/21 01:18:15]

I presume you've thought about the downloads page and don't believe that the
safe->dangerous transition will cause any UI problems?  (I don't think so, but I
think you're in a better position to say than I am.)

[benjhayden, 2011/11/21 16:21:55]

It looks to me like Download.prototype.update supports this, but a manual test
would make me feel better. :-)

[asanka, 2011/11/21 17:08:57]

I verified the behavior manually for the downloads page. I've yet to verify it
for the active_downloads page.

 }
 
 /**
@@ -347,6 +348,7 @@ Download.prototype.update = function(download) {
       this.dangerDesc_.textContent = localStrings.getStringF('danger_file_desc',
                                                              this.fileName_);
     } else {
+      // This is used by both DANGEROUS_URL and DANGEROUS_CONTENT.
       this.dangerDesc_.textContent = localStrings.getString('danger_url_desc');
     }
     this.danger_.style.display = 'block';
@@ -462,6 +464,7 @@ Download.prototype.getStatusText_ = function() {
     case Download.States.PAUSED:
       return localStrings.getString('status_paused');
     case Download.States.DANGEROUS:
+      // danger_url_desc is also used by DANGEROUS_CONTENT
       var desc = this.dangerType_ == Download.DangerType.DANGEROUS_FILE ?
           'danger_file_desc' : 'danger_url_desc';
       return localStrings.getString(desc);