summaryrefslogtreecommitdiffstats
path: root/extensions
diff options
context:
space:
mode:
Diffstat (limited to 'extensions')
-rw-r--r--extensions/common/switches.cc8
-rw-r--r--extensions/common/switches.h1
2 files changed, 9 insertions, 0 deletions
diff --git a/extensions/common/switches.cc b/extensions/common/switches.cc
index 306f85a..c416ac9 100644
--- a/extensions/common/switches.cc
+++ b/extensions/common/switches.cc
@@ -60,7 +60,15 @@ const char kForceDevModeHighlighting[] = "force-dev-mode-highlighting";
const char kGlobalCommands[] = "global-commands";
// Notify the user and require consent for extensions running scripts.
+// Appending --scripts-require-action=1 has the same effect as
+// --enable-scripts-require-action (see below).
const char kScriptsRequireAction[] = "scripts-require-action";
+// FeatureSwitch and about_flags don't play nice. Feature switch expects either
+// --enable-<feature> or --<feature>=1, but about_flags expects the command
+// line argument to enable it (or a selection). Hack this in, so enabling it
+// in about_flags enables the feature. Appending this flag has the same effect
+// as --scripts-require-action=1.
+const char kEnableScriptsRequireAction[] = "enable-scripts-require-action";
// Makes component extensions appear in chrome://settings/extensions.
const char kShowComponentExtensionOptions[] =
diff --git a/extensions/common/switches.h b/extensions/common/switches.h
index f27d782..2faaad4 100644
--- a/extensions/common/switches.h
+++ b/extensions/common/switches.h
@@ -27,6 +27,7 @@ extern const char kExtensionsOnChromeURLs[];
extern const char kForceDevModeHighlighting[];
extern const char kGlobalCommands[];
extern const char kScriptsRequireAction[];
+extern const char kEnableScriptsRequireAction[];
extern const char kShowComponentExtensionOptions[];
extern const char kWhitelistedExtensionID[];