Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(3947)

Unified Diff: chrome/browser/extensions/settings/settings_backend.cc

Issue 8587025: Extension settings API: force through changes that come from sync (ignoring (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 9 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/browser/extensions/settings/settings_backend.cc
diff --git a/chrome/browser/extensions/settings/settings_backend.cc b/chrome/browser/extensions/settings/settings_backend.cc
index 2a6fee5f2e7c91532d65d37c5eef0a0ccbd80811..8ca34c953954cf012f8ee2f83ee4dd463471d3e1 100644
--- a/chrome/browser/extensions/settings/settings_backend.cc
+++ b/chrome/browser/extensions/settings/settings_backend.cc
@@ -110,7 +110,7 @@ void SettingsBackend::DeleteStorage(const std::string& extension_id) {
// Clear settings when the extension is uninstalled. Leveldb implementations
// will also delete the database from disk when the object is destroyed as
// a result of being removed from |storage_objs_|.
- maybe_storage->second->Clear();
+ maybe_storage->second->Clear(SettingsStorage::FORCE);
storage_objs_.erase(maybe_storage);
}

Powered by Google App Engine
This is Rietveld 408576698