Fullscreen JS API implementation.

content/common/view_messages.h

Index: content/common/view_messages.h
diff --git a/content/common/view_messages.h b/content/common/view_messages.h
index 974f3e86b0a5a705bb864c346edf9f7f3afdd20d..7bca1c46307549d7e1227b569737b4e39d3b14d9 100644
--- a/content/common/view_messages.h
+++ b/content/common/view_messages.h
@@ -1200,6 +1200,9 @@ IPC_MESSAGE_ROUTED2(ViewMsg_SavePageAsMHTML,
                     int /* job_id */,
                     IPC::PlatformFileForTransit /* file handle */)
 
+// Exit fullscreen.
+IPC_MESSAGE_ROUTED0(ViewMsg_ExitFullscreen)
+
 // Messages sent from the renderer to the browser.
 
 // Sent by the renderer when it is creating a new window.  The browser creates
@@ -1960,6 +1963,10 @@ IPC_MESSAGE_ROUTED2(ViewHostMsg_UpdateInspectorSetting,
                     std::string,  /* key */
                     std::string /* value */)
 
+// Puts the browser into fullscreen mode.

[Peter Kasting, 2011/08/15 22:42:54]

Nit: Slightly more commentary about tab- versus browser-fullscreen mode?

[koz (OOO until 15th September), 2011/08/16 07:06:55]

Good point. I've extended the comment slightly - I feel like the only
differences between "browser" and "tab" fullscreen are minor behavioural
differences that only manifest in the handling of edge cases, so the code here
wouldn't benefit from too much more of an explanation.

+IPC_MESSAGE_ROUTED1(ViewHostMsg_ToggleFullscreen,
+                    bool /* enter_fullscreen */);
+
 // Send back a string to be recorded by UserMetrics.
 IPC_MESSAGE_CONTROL1(ViewHostMsg_UserMetricsRecordAction,
                      std::string /* action */)