`chrome.browsingData` extension API can now remove data from protected origins.

chrome/common/extensions/api/browsing_data.json

Index: chrome/common/extensions/api/browsing_data.json
diff --git a/chrome/common/extensions/api/browsing_data.json b/chrome/common/extensions/api/browsing_data.json
index 7ba52ccc94be068be750f451ce0feeffe6354bd1..4ed71721bd4756977802470c7725fdefae6d028e 100644
--- a/chrome/common/extensions/api/browsing_data.json
+++ b/chrome/common/extensions/api/browsing_data.json
@@ -15,6 +15,15 @@
             "type": "number",
             "optional": true,
             "description": "Remove data accumulated on or after this date, represented in milliseconds since the epoch (accessible via the <code>getTime</code> method of the JavaScript <code>Date</code> object). If absent, defaults to 0 (which would remove all browsing data)."
+          },
+          "origin_types": {
+            "type": "array",

[Bernhard Bauer, 2012/06/04 11:20:16]

Would it make sense to have this as an object with keys "unprotected_web" and
"protected_web" like the dataToRemove parameter below?

[Mike West, 2012/06/04 12:23:39]

It might. It probably does, actually.

I should have read this before I addressed your other points in the other file.
:)

+            "optional": true,
+            "description": "Array of origin types that should be effected: 'unprotected_web' refers to normal websites, 'protected_web' refers to websites that have been installed as hosted applications. This setting defaults to ['unprotected_web']. Please ensure that you <em>really</em> want to remove application data before adding 'protected_web'.",

[Bernhard Bauer, 2012/06/04 11:20:16]

Nit: "affected"

[Mike West, 2012/06/04 12:23:39]

Done.

+            "items": {
+              "type": "string",
+              "enum": ["unprotected_web", "protected_web"]
+            }
           }
         }
       }