Initial support for web-extent background pages.

This patch adds a new RVH container: BackgroundContents. The idea is that apps can open a live web-page as a "background" page using window.open('<url>', '<name>', 'background');

If 'background' is specified and the opener is within the app's extent, a BackgroundContents will be used. Otherwise, the 'background' feature is ignored and it is treated as a regular popup call.

Note that as of this patch the following are explicitly not-yet addressed:

1) Session storage for BackgroundContents
2) SSL (or other failures) requiring UI
3) Javascript messages (alert, etc...)
4) Session restore

TEST=All tests should pass
BUG=41275

Review URL: http://codereview.chromium.org/1734014

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46544 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 3 insertions, 3 deletions

diff --git a/chrome/renderer/render_view.h b/chrome/renderer/render_view.h
index 1eda03e..ab2b4a4 100644
--- a/chrome/renderer/render_view.h
+++ b/chrome/renderer/render_view.h
@@ -771,8 +771,8 @@ class RenderView : public RenderWidget,
   void OnAutoFillFormDataFilled(int query_id,
                                 const webkit_glue::FormData& form);
 
-  // Message that the popup notification has been shown or hidden.
-  void OnPopupNotificationVisibilityChanged(bool visible);
+  // Message that script may use window.close().
+  void OnAllowScriptToClose(bool script_can_close);
 
   // Handles messages posted from automation.
   void OnMessageFromExternalHost(const std::string& message,
@@ -1086,7 +1086,7 @@ class RenderView : public RenderWidget,
   // is being displayed. We instead assume that when we create a window off
   // this RenderView, that it is going to be blocked until we get a message
   // from the Browser process telling us otherwise.
-  bool popup_notification_visible_;
+  bool script_can_close_;
 
   // True if the browser is showing the spelling panel for us.
   bool spelling_panel_visible_;