Tabs API is usable without tabs permission.

chrome/common/extensions/permissions/permission_set.cc

Index: chrome/common/extensions/permissions/permission_set.cc
diff --git a/chrome/common/extensions/permissions/permission_set.cc b/chrome/common/extensions/permissions/permission_set.cc
index fde8fee03847d3545e8736d58d454aded2ca238d..5918294f2ce3325d74a5c59f6b861786359dd81c 100644
--- a/chrome/common/extensions/permissions/permission_set.cc
+++ b/chrome/common/extensions/permissions/permission_set.cc
@@ -58,9 +58,31 @@ const size_t kNumNonPermissionModuleNames =
 // use with no permissions specified.
 const char* kNonPermissionFunctionNames[] = {
   "management.getPermissionWarningsByManifest",

[Matt Tytel, 2012/08/06 18:45:23]

Ignorant Drive-by comment: Should executeScript should require permission since
they'll have access to the tab data? Or is that covered in the "http://*/*"
permissions?

Maybe insertCSS too for tab editing reasons.

+  "tabs.captureVisibleTab",
+  "tabs.connect",
   "tabs.create",
+  "tabs.detectLanguage",
+  "tabs.executeScript",
+  "tabs.get",
+  "tabs.getCurrent",
+  "tabs.getSelected",
+  "tabs.highlight",
+  "tabs.insertCSS",
+  "tabs.move",
+  "tabs.onActivated",
+  "tabs.onActiveChanged",
+  "tabs.onAttached",
+  "tabs.onCreated",
+  "tabs.onDetached",
+  "tabs.onHighlighted",
+  "tabs.onMoved",
+  "tabs.onSelectionChanged",
+  "tabs.onUpdated",
   "tabs.onRemoved",
+  "tabs.query",
+  "tabs.reload",
   "tabs.remove",
+  "tabs.sendMessage",
   "tabs.update",
 };
 const size_t kNumNonPermissionFunctionNames =