Begin whitelisting specific extensions for global key registration.

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 37830a422afb9dcf5ef99efe9b354c883c570d26..f40d314f22b3a53ff6730c744489a35948ddb538 100644
--- a/chrome/common/extensions/api/_permission_features.json
+++ b/chrome/common/extensions/api/_permission_features.json
@@ -297,6 +297,14 @@
     "extension_types": ["extension", "legacy_packaged_app", "platform_app"],
     "location": "component"
   },
+  "commands.accessibility": {
+    "channel": "stable",
+    "extension_types": ["extension", "legacy_packaged_app", "platform_app"],
+    "whitelist": [
+      "2FCBCE08B34CCA1728A85F1EFBD9A34DD2558B2E",
+      "75C7F4B720314B6CB1B5817CD86089DB95CD2461"
+    ]
+  },

[Finnur, 2014/08/21 11:18:10]

See comments at the top of the file for additional steps.

I also discovered an email thread that is relevant. Let me add you to it.

[David Tseng, 2014/08/21 16:17:56]

Was previously done; other than making note of the mapping of SHA-1 back to id,
was there anything else?
Got it; thanks.

[Finnur, 2014/08/21 16:23:32]

I'm not sure if more is needed. Lets see what comes out of the email thread.

   "contentSettings": {
     "channel": "stable",
     "extension_types": ["extension", "legacy_packaged_app"]