From 6b55790a01949ceed731555e7f0da6c7d13d35cd Mon Sep 17 00:00:00 2001 From: "mkwst@chromium.org" Date: Thu, 15 Dec 2011 14:05:05 +0000 Subject: Reland of r114615: "chrome.clear: Increasing granularity of public API" http://codereview.chromium.org/7717023 added more granular options to BrowsingDataRemover. This CL exposes those options to the chrome.clear extension API. Among other things, this means that chrome.clear.cookies() will _only_ clear cookies, not cookies and site data. At the moment, clearing any quota managed data type will clear them all. That is being addressed in http://codereview.chromium.org/7839029/ but is independent from changing the public interface. BUG=94334 TEST=browser_tests Review URL: http://codereview.chromium.org/8952014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114630 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/browsing_data_remover.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'chrome/browser/browsing_data_remover.h') diff --git a/chrome/browser/browsing_data_remover.h b/chrome/browser/browsing_data_remover.h index 0257815..8e2bbf7 100644 --- a/chrome/browser/browsing_data_remover.h +++ b/chrome/browser/browsing_data_remover.h @@ -128,7 +128,7 @@ class BrowsingDataRemover : public content::NotificationObserver, private: // The clear API needs to be able to toggle removing_ in order to test that // only one BrowsingDataRemover instance can be called at a time. - FRIEND_TEST_ALL_PREFIXES(ExtensionApiTest, ClearOneAtATime); + FRIEND_TEST_ALL_PREFIXES(ExtensionClearTest, OneAtATime); enum CacheState { STATE_NONE, -- cgit v1.1