Enable Pointer Lock for packaged apps using ShellWindow.

chrome/common/extensions/permissions/api_permission.cc

Index: chrome/common/extensions/permissions/api_permission.cc
diff --git a/chrome/common/extensions/permissions/api_permission.cc b/chrome/common/extensions/permissions/api_permission.cc
index 114f35d127b00d1bba76a1f0693bd73290cbeee1..f28374d271c409e2e34904c6238e73a830a79a6a 100644
--- a/chrome/common/extensions/permissions/api_permission.cc
+++ b/chrome/common/extensions/permissions/api_permission.cc
@@ -326,6 +326,9 @@ void APIPermissionInfo::RegisterAllPermissions(
     { APIPermission::kUsb, "usb", kFlagNone,
       IDS_EXTENSION_PROMPT_WARNING_USB,
       PermissionMessage::kUsb },
+    { APIPermission::kPointerLock, "pointerLock", kFlagNone,
+      IDS_EXTENSION_PROMPT_WARNING_POINTER_LOCK,

[asargent_no_longer_on_chrome, 2012/11/28 20:32:13]

We should ask Erik's opinion about whether this permission rises to the level of
something we should explicitly mention in the install dialog.

For context, in the past we've taken the position that we want fine-granularity
for the permissions developers need to specify in their manifest, but much
rougher granularity in the install confirmation messages we actually show to
human users. In many cases we've decided to elide warnings about
"trivial/nuisance" permissions that don't have particularly dire security
implications (keeping in mind that installing an app is a more explicit user
action than loading an iframe with a potentially compromised ad network on some
random website), and I wonder whether pointer lock should be considered that
way.

[scheib, 2012/11/28 20:58:12]

Looping Erik in.

[Erik does not do reviews, 2012/11/30 01:11:06]

Nope, we don't need a permission string for pointer lock, full screen or
gamepad.

+      PermissionMessage::kPointerLock },
   };
 
   for (size_t i = 0; i < ARRAYSIZE_UNSAFE(PermissionsToRegister); ++i) {