Move declarative API into events API

chrome/common/extensions/api/_permission_features.json

Index: chrome/common/extensions/api/_permission_features.json
diff --git a/chrome/common/extensions/api/_permission_features.json b/chrome/common/extensions/api/_permission_features.json
index 4ecd3b48fdf30d453055f1dfc9642286ca54343d..4b0ce89bdcd0a99fa8085448c150a0e1ff66282e 100644
--- a/chrome/common/extensions/api/_permission_features.json
+++ b/chrome/common/extensions/api/_permission_features.json
@@ -78,12 +78,6 @@
     "channel": "stable",
     "extension_types": ["extension", "packaged_app", "platform_app"]
   },
-  // TODO(battre): Remove "declarative" permission when APIs can be set to
-  // dev-only, without having to have a permission. See: crbug.com/120069.
-  "declarative": {
-    "channel": "dev",
-    "extension_types": ["extension", "packaged_app"]

[battre, 2012/05/09 16:28:08]

I did not introduce a new feature "events". I am not sure whether this is
necessary. I introduce an "events" permission but grant it to all extensions. If
this should contain "events", what would the "extension_types" be?

[Aaron Boodman, 2012/05/09 19:29:46]

No permission is needed. Every extension is going to need "events".

-  },
   "declarativeWebRequest": {
     "channel": "dev",
     "extension_types": ["extension", "packaged_app"]