fullscreen in apps v2 ShellWindow via app.window.create.

chrome/common/extensions/api/app_current_window_internal.idl

Index: chrome/common/extensions/api/app_current_window_internal.idl
diff --git a/chrome/common/extensions/api/app_current_window_internal.idl b/chrome/common/extensions/api/app_current_window_internal.idl
index c063bea12049b84b43e06501106fa84b4ad41320..bf33d920f115324692493fa81ca82a4654150dfa 100644
--- a/chrome/common/extensions/api/app_current_window_internal.idl
+++ b/chrome/common/extensions/api/app_current_window_internal.idl
@@ -19,6 +19,7 @@
 
   interface Functions {
     static void focus();
+    static void fullscreen();

[jeremya, 2013/04/05 20:00:35]

I've forgotten why we decided that having an apps-specific fullscreen API was
necessary. Something to do with the webkit, err, blink API not being able to
specify fullscreen on launch?

[scheib, 2013/04/05 21:47:52]

https://code.google.com/p/chromium/issues/detail?id=163626
Yes:
- Fullscreen on create
- Fullscreen at the application's control without limitations such as HTML5's
required user gesture.
- Fullscreen for the app window without confusing web content that doesn't
expect to be in a fullscreen state unless it caused its self to go fullscreen.

[jeremya, 2013/04/08 17:13:54]

#1 and #2 could be fixed with a judicious blink change, I think. Could you
expand on #3? It seems like the web API should be able to deal with that case...
possibly with the application of <iframe>s.

In general, if we can stick to using web APIs in apps, we should do that as much
as possible.

     static void minimize();
     static void maximize();
     static void restore();