Sandbox windows not provided to chrome.app.window.create.

chrome/common/extensions/docs/templates/articles/app_external.html

 <h1>External Content</h1>
 
 
 <p>
 The <a href="app_architecture#security">Chrome Apps security model</a> disallows
 external content in iframes and
 the use of inline scripting and <code>eval()</code>.
 You can override these restrictions,
 but your external content must be isolated from the app.
 </p>
@@ skipping 160 matching lines @@
 <h3 id="opening_sandbox">Opening a sandboxed page in a window</h3>
 
 <p>
 Just like any other app pages,
 you can create a window that the sandboxed page opens in.
 Here's a sample that creates two windows,
 one for the main app window that isn't sandboxed,
 and one for the sandboxed page:
 </p>
 
-<p class="warning">
+<p class="note">
 NOTE:
-<a href="https://code.google.com/p/chromium/issues/detail?id=154662">issue 154662</a>
-is a bug when using sandbox pages to create windows.
-The effect is that an error "Uncaught TypeError: Cannot call method
-'initializeAppWindow' of undefined" is output to the developer console
-and that the app.window.create call does not call the callback function
-with a window object. However, the sandbox page is created as a new window.
+A sandboxed window will not have access to the chrome.app APIs. If a
+callback is provided to app.window.create it will be run, but will not have
+the sandboxed window provided to it.
 </p>
 
 <pre data-filename="background.js">
 chrome.app.runtime.onLaunched.addListener(function() {
   chrome.app.window.create('window.html', {
     'bounds': {
       'width': 400,
       'height': 400,
       'left': 0,
       'top': 0
@@ skipping 98 matching lines @@
 
 window.addEventListener('message', messageHandler);
 </pre>
 
 <p>
 For more details, check out the
 <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/sandbox">sandbox</a> sample.
 </p>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>