Plugin Power Saver: Overhaul plugin-power-saver flags. Show in UI.

components/plugins/common/plugins_switches.cc

Index: components/plugins/common/plugins_switches.cc
diff --git a/components/plugins/common/plugins_switches.cc b/components/plugins/common/plugins_switches.cc
new file mode 100644
index 0000000000000000000000000000000000000000..64384fce0082372bfaf206c3f8488c9685a03cfe
--- /dev/null
+++ b/components/plugins/common/plugins_switches.cc
@@ -0,0 +1,15 @@
+// Copyright 2015 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "components/plugins/common/plugins_switches.h"
+
+namespace switches {
+
+// Disables forcing on the experimental Plugin Power Saver feature.
+const char kDisableForcePluginPowerSaver[] = "disable-force-plugin-power-saver";
+
+// Enables forcing on the experimental Plugin Power Saver feature.
+const char kEnableForcePluginPowerSaver[] = "enable-force-plugin-power-saver";

[tommycli, 2015/03/27 22:09:39]

I'm kind of torn on whether or not I should rename this to:

--enable-force-plugin-power-saver

The flag overrides the content setting and turns PPS on. Without the flag, it
just follows the user's content setting.

We have --disable-force-plugin-power-saver because we want to allow Googlers to
opt-out of the experiment if they desire.

Would it be better/simpler if we just called it:

--enable-plugin-power-saver
--disable-plugin-power-saver

?

I worry it may be somewhat confusing either way.

+
+}  // namespace switches