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 1303385249f6b14316cfa871787b772c460033ee..25374d80fda98578dcf0b436a1800e9c0b42626e 100644
--- a/chrome/common/extensions/api/app_window.idl
+++ b/chrome/common/extensions/api/app_window.idl
@@ -348,6 +348,14 @@ 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

[Jamie, 2014/05/23 22:13:10]

Chromium style is 80-character limit for most languages.

[Sriram, 2014/05/23 22:20:06]

Done.

+    // not sent. This currently works only when the windows is in fullscreen. Requires the
+    // <code>"requestAllKeys"</code> permission.
+    static void setRequestAllKeys(boolean requestAllKeys);
+
+    // Return current state of "RequestAllKeys" state.
+    static boolean getRequestAllKeys();

[Jamie, 2014/05/23 22:13:10]

I don't think the getter is necessary (setAlwaysOnTop doesn't have one, for
example). If there's a valid use-case for knowing whether or not you're going to
receive all keyboard events, then an event is probably a better solution, since
the state can change asynchronously: It becomes false if another window gains
focus and it becomes true when the user gives the app permission to activate the
feature for the first time.

On the whole, though, I don't think being able to query this is very useful.

[Sriram, 2014/05/23 22:20:06]

Done.

+
     // The JavaScript 'window' object for the created child.
     [instanceOf=Window] object contentWindow;