MD Settings: Add feature flag for showing content settings in a per-origin view.

chrome/common/chrome_switches.h

Index: chrome/common/chrome_switches.h
diff --git a/chrome/common/chrome_switches.h b/chrome/common/chrome_switches.h
index a45b3f6ca98003e6afca96ae9b1fd63464a18e75..8bf205f3a5233f605441a86ada8d5f5aa7e3ed85 100644
--- a/chrome/common/chrome_switches.h
+++ b/chrome/common/chrome_switches.h
@@ -130,6 +130,7 @@ extern const char kEnableProfiling[];
 extern const char kEnablePushApiBackgroundMode[];
 extern const char kEnableQuic[];
 extern const char kEnableSettingsWindow[];
+extern const char kEnableSiteDetails[];

[dominickn, 2017/05/05 02:58:53]

Instead of having a switch, can you add a feature instead? Features are the
"right way" to do this now. For instance, you can have a look at
features::kModalPermissionPrompts, which has a chrome://flags entry and can be
enabled on the command line with --enable-features=ModalPermissionPrompts.

It's not that much different from your CL now:
 - add the feature in chrome/common/chrome_features*
 - remove the switch
 - change the about:flags entry and histograms value to pick up the feature

I looked at the CL where site settings added this flag and it looks like they
were a bit behind the times when they added it (crrev.com/2409003002)

[Patti Lor, 2017/05/05 08:45:21]

Done, thank you!

 extern const char kEnableSiteEngagementEvictionPolicy[];
 extern const char kEnableSiteSettings[];
 extern const char kEnableSupervisedUserManagedBookmarksFolder[];