Add an experimental permissions API for extensions.

chrome/test/data/extensions/api_test/permissions/optional/manifest.json

Index: chrome/test/data/extensions/api_test/permissions/optional/manifest.json
diff --git a/chrome/test/data/extensions/api_test/permissions/optional/manifest.json b/chrome/test/data/extensions/api_test/permissions/optional/manifest.json
new file mode 100644
index 0000000000000000000000000000000000000000..ad8e32bd5c51add89494e312050be3af907d29f2
--- /dev/null
+++ b/chrome/test/data/extensions/api_test/permissions/optional/manifest.json
@@ -0,0 +1,14 @@
+{
+   "name": "permissions/optional",
+   "description": "permissions/optional",
+   "key": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDkprt3BRSqoikAhSygI6VUzDLt18cKODYmkaa/dwPp4dboyz93RSB+v76grbqsNWrJjkrEwRD3QFeBYBq7h27XAMV4X5XvWjmWQBkRTBQyQI8cZd7M9dgfKrI3EqX9OJvd/wTJkC0dgF47nwWRa/Tvwl7Y66GwEEUjpn2MTv4klwIDAQAB",

[Mihai Parparita -not on Chrome, 2011/07/20 22:03:43]

Is the key necessary?

[jstritar, 2011/07/22 19:21:55]

The key makes sure the extension has the same ID, so we can initialize the
extension's permission prefs before running the tests. (One test verifies the
extension can request permissions with no user prompt if they are already in the
granted permissions list)

+   "version": "0.1",
+   "background_page": "background.html",
+   "permissions": [ "management", "permissions", "http://example.org/" ],
+   "optional_permissions": [
+     "tabs",
+     "management",
+     "notifications",
+     "background"
+   ]
+}