Cache the object given to the chrome.app.window.create callback

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 9dca0a3706de6a2dcc08a942cbf6afbb63897e63..5aac989e1d4ffd19a69067d049639d2b4e4effcb 100644
--- a/chrome/common/extensions/api/app_window.idl
+++ b/chrome/common/extensions/api/app_window.idl
@@ -109,5 +109,6 @@ namespace app.window {
                        optional CreateWindowCallback callback);
 
     [nocompile] static AppWindow current();
+    [internal, nocompile] static void makeAppWindow(object state);

[jeremya, 2012/09/19 16:13:15]

I don't think [internal] means anything when applied to functions; generally
it's specified on the namespace and its behaviour is to move it into the
chromeHidden.internalAPIs namespace. So as is, client code would be able to call
this function.

Perhaps a better way to do this would be to pass windowParams through to
GetView() whole, and then have GetView() pass it to a method in platform_app.js
via module_system()->CallModuleMethod() (as in
chrome/renderer/extensions/app_window_custom_bindings.cc). Ask koz about this
too :)

[tapted, 2012/09/25 21:27:22]

 dropped 'internal'

   };
 };