Add module-level permissions to extensions.

This first pass is fairly simple. If a permission is not specified in the
manifest, the corresponding module will not be exposed to script. For example,
without specifying the "tabs" permission, chrome.tabs and chrome.windows will
not be available.

BUG=12140
TEST=no

Review URL: http://codereview.chromium.org/164039

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22745 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 2 insertions, 2 deletions

diff --git a/chrome/renderer/resources/extension_process_bindings.js b/chrome/renderer/resources/extension_process_bindings.js
index 7218d03..1e33cb9 100644
--- a/chrome/renderer/resources/extension_process_bindings.js
+++ b/chrome/renderer/resources/extension_process_bindings.js
@@ -14,7 +14,7 @@ var chrome = chrome || {};
 (function() {
   native function GetExtensionAPIDefinition();
   native function StartRequest();
-  native function GetCurrentPageActions();
+  native function GetCurrentPageActions(extensionId);
   native function GetViews();
   native function GetChromeHidden();
   native function GetNextRequestId();
@@ -186,7 +186,7 @@ var chrome = chrome || {};
 
   // Page action events send (pageActionId, {tabId, tabUrl}).
   function setupPageActionEvents(extensionId) {
-    var pageActions = GetCurrentPageActions();
+    var pageActions = GetCurrentPageActions(extensionId);
     var eventName = "";
     for (var i = 0; i < pageActions.length; ++i) {
       eventName = extensionId + "/" + pageActions[i];