Ensure content settings aren't persisted in the guest profile

components/content_settings/core/browser/content_settings_default_provider.cc

Index: components/content_settings/core/browser/content_settings_default_provider.cc
diff --git a/components/content_settings/core/browser/content_settings_default_provider.cc b/components/content_settings/core/browser/content_settings_default_provider.cc
index 8bae69fad05db85f228ff811c61b86bf42d8f9c0..9cd6eba3792e6eef889c0d338605e4c6ec316699 100644
--- a/components/content_settings/core/browser/content_settings_default_provider.cc
+++ b/components/content_settings/core/browser/content_settings_default_provider.cc
@@ -208,14 +208,15 @@ bool DefaultProvider::SetWebsiteSetting(
     return false;
   }
 
+  // Put |in_value| in a scoped pointer to ensure that it gets cleaned up
+  // properly if we don't pass on the ownership.
+  scoped_ptr<base::Value> value(in_value);
+
   // The default settings may not be directly modified for OTR sessions.
   // Instead, they are synced to the main profile's setting.
   if (is_incognito_)
-    return false;
+    return true;
 
-  // Put |in_value| in a scoped pointer to ensure that it gets cleaned up
-  // properly if we don't pass on the ownership.
-  scoped_ptr<base::Value> value(in_value);
   {
     base::AutoReset<bool> auto_reset(&updating_preferences_, true);
     // Lock the memory map access, so that values are not read by