Move UserScript and Extension switches to top-level extensions/.

extensions/common/switches.cc

+// Copyright 2013 The Chromium Authors. All rights reserved.

[Matt Perry, 2013/07/17 22:28:30]

Any reason you picked these 4 switches? This is a small subset of
extensions-related switches.

[Yoyo Zhou, 2013/07/17 22:36:14]

These are the ones that are used in extension.cc. There are definitely a few
more that are in the files Extension depends on, but I thought I'd just get
started with these. (And e.g. I didn't want to touch
kEnableExperimentalExtensionApis because that's used in a million places.)

+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "extensions/common/switches.h"
+
+namespace extensions {
+
+namespace switches {
+
+// Allows the browser to load extensions that lack a modern manifest when that
+// would otherwise be forbidden.
+const char kAllowLegacyExtensionManifests[] =
+    "allow-legacy-extension-manifests";
+
+// Allows injecting extensions and user scripts on the extensions gallery
+// site. Normally prevented for security reasons, but can be useful for
+// automation testing of the gallery.
+const char kAllowScriptingGallery[]         = "allow-scripting-gallery";
+
+// Enables extensions running scripts on chrome:// URLs.
+// Extensions still need to explicitly request access to chrome:// URLs in the
+// manifest.
+const char kExtensionsOnChromeURLs[]        = "extensions-on-chrome-urls";
+
+// Makes component extensions appear in chrome://settings/extensions.
+const char kShowComponentExtensionOptions[] =
+    "show-component-extension-options";
+
+}  // namespace switches
+
+}  // namespace extensions