extensions: windows: list all windows from the current profile

chrome/common/extensions/permissions/chrome_api_permissions.cc

Index: chrome/common/extensions/permissions/chrome_api_permissions.cc
diff --git a/chrome/common/extensions/permissions/chrome_api_permissions.cc b/chrome/common/extensions/permissions/chrome_api_permissions.cc
index 92bb884a0c6a6a227d20623e383984bcbbd99fad..508f797d4654d346fee77801bdd373e63a346786 100644
--- a/chrome/common/extensions/permissions/chrome_api_permissions.cc
+++ b/chrome/common/extensions/permissions/chrome_api_permissions.cc
@@ -17,6 +17,7 @@ namespace extensions {
 namespace {
 
 const char kWindowsPermission[] = "windows";
+const char kWindowsGlobalPermission[] = "windows.global";
 
 template <typename T>
 APIPermission* CreateAPIPermission(const APIPermissionInfo* permission) {
@@ -189,6 +190,11 @@ std::vector<APIPermissionInfo*> ChromeAPIPermissions::GetAllPermissions()
        APIPermissionInfo::kFlagNone,
        IDS_EXTENSION_PROMPT_WARNING_HISTORY_READ,
        PermissionMessage::kTabs},
+      {APIPermission::kTabGlobal,
+       "tabs.global",
+       APIPermissionInfo::kFlagNone,
+       IDS_EXTENSION_PROMPT_WARNING_HISTORY_READ,

[not at google - send to devlin, 2015/04/20 16:47:43]

Extensions can usually enumerate Chrome tabs/windows without any permission. The
tabs/windows permissions just give them access to sensitive data like the URL.

It makes sense to me to continue that behavior, which is to say, don't make
tabs.global/windows.global require a permission warning, and don't make it grant
access to data like the URL.

Also I think that windows.global is enough, no reason to have the tabs.global
alias.

[llandwerlin-old, 2015/06/26 11:26:14]

Done.

[not at google - send to devlin, 2015/06/30 17:33:53]

Mm actually I need to think about this a little bit more. It's the right thing
to do to (a) force extensions to opt-in to getting global windows (otherwise
it's not backwards compatible), and (b) not require an install warning just to
do so.

However, it's also useful to read the URLs (like the extensions) of windows,
which does require an install warning.

My current thinking is to actually use an entirely different namespace for this,
like chrome.windows.global.query/remove/onCreated/onUpdated/..., then to have
the windows.global permission give access to the URLs and so on. That would be
both backwards compatible and fairly clean.

But that's probably a much larger change, and I'm sure we can carve out plenty
of code to submit before making that decision (like all of the event routing and
querying stuff, most of the app window router).

Sorry to drop this on you now.

Another option would be to have 2 separate permissions but instinctively that
sounds confusing.

+       PermissionMessage::kTabsGlobal},
       {APIPermission::kTopSites,
        "topSites",
        APIPermissionInfo::kFlagNone,
@@ -453,6 +459,8 @@ ChromeAPIPermissions::GetAllAliases() const {
   // Register aliases.
   std::vector<PermissionsProvider::AliasInfo> aliases;
   aliases.push_back(PermissionsProvider::AliasInfo("tabs", kWindowsPermission));
+  aliases.push_back(
+      PermissionsProvider::AliasInfo("tabs.global", kWindowsGlobalPermission));
   return aliases;
 }