API proposal for chrome.app.window to intercept all keys.

chrome/common/extensions/api/app_window.idl

Index: chrome/common/extensions/api/app_window.idl
diff --git a/chrome/common/extensions/api/app_window.idl b/chrome/common/extensions/api/app_window.idl
index b08037bf327bddf1dfbb1ba6e508493e54cff19d..67906ab3457204882331958ba5138060702c102a 100644
--- a/chrome/common/extensions/api/app_window.idl
+++ b/chrome/common/extensions/api/app_window.idl
@@ -351,6 +351,12 @@ namespace app.window {
     // <code>"alwaysOnTopWindows"</code> permission.
     static void setAlwaysOnTop(boolean alwaysOnTop);
 
+    // Set whether the window should get all keyboard events including system
+    // keys that are usually not sent. This currently works only when the
+    // windows is in fullscreen. Requires the <code>"app.window.allKeys"</code>
+    // permission.
+    static void setWantAllKeys(boolean wantAllKeys);
+
     // The JavaScript 'window' object for the created child.
     [instanceOf=Window] object contentWindow;
 
@@ -435,5 +441,11 @@ namespace app.window {
 
     // Event for testing. Lets tests wait until a window has been shown.
     [nocompile, nodoc] static void onWindowFirstShown();
+
+    // Fired when WantAllKeys setting is in effect.
+    [nocompile] static void onWantAllKeysSettingEffective();
+
+    // Fired when WantAllKeys setting is no longer in effect.
+    [nocompile] static void onWantAllKeysSettingLost();

[Jamie, 2014/06/25 16:46:58]

As discussed off-line, I think one event and a getter would be cleaner than two
events. I also don't really like these names. How about something like
onAllKeysInterceptChanged? You might also want to change setWantAllKeys to
setInterceptAllKeps for symmetry (though I have no problem with the current name
for that).

   };
 };