Propagate the SafeBrowsing download protection verdict to the DownloadItem.

chrome/common/extensions/api/extension_api.json

Index: chrome/common/extensions/api/extension_api.json
diff --git a/chrome/common/extensions/api/extension_api.json b/chrome/common/extensions/api/extension_api.json
index 08ddcd8290030f5573d80ea5cfd43fc9dee2825d..0486385be3aea56411b59b2104cbad0055c959ea 100644
--- a/chrome/common/extensions/api/extension_api.json
+++ b/chrome/common/extensions/api/extension_api.json
@@ -4315,7 +4315,12 @@
       "DANGER_URL": {
         "type": "string",
         "value": "url",
-        "description": "The download's URL is suspicious."
+        "description": "The download's URL is malicious."

[Mihai Parparita -not on Chrome, 2011/11/17 20:30:25]

Is the change to "malicious" here but the keeping of "suspicious" above for
DANGER_FILE intentional?

[noelutz, 2011/11/17 21:25:16]

It is.

DANGER_FILE == filename is suspicious. E.g., .exe, .dmg
DANGER_URL == SafeBrowsing servers have seen malware on this URL before.
DANGER_CONTENT == SafeBrowsing servers have seen this content before and flagged
it as malicious.

+      },
+      "DANGER_CONTENT": {
+        "type": "string",
+        "value": "content",
+        "description": "The download's content is malicious."
       }
     },
     "types": [