Fullscreen JS API implementation.

chrome/browser/ui/browser.cc

Index: chrome/browser/ui/browser.cc
diff --git a/chrome/browser/ui/browser.cc b/chrome/browser/ui/browser.cc
index 34c7cdd9e223c36e2173be01bb023ce2e25254ae..13c27afc8db152dd4cd0d0702595260e4122c081 100644
--- a/chrome/browser/ui/browser.cc
+++ b/chrome/browser/ui/browser.cc
@@ -3477,6 +3477,18 @@ content::JavaScriptDialogCreator* Browser::GetJavaScriptDialogCreator() {
   return GetJavaScriptDialogCreatorInstance();
 }
 
+void Browser::EnterFullscreenMode() {
+  if (window_->IsFullscreen())

[scherkus (not reviewing), 2011/07/28 22:43:08]

are these DCHECK worthy or plausible calls?

[sky, 2011/07/28 22:45:38]

Since the user can always enter/exit fullscreen at their discretion it doesn't
seem like they should be DCHECKs.

[koz (OOO until 15th September), 2011/07/29 04:12:58]

Right - there's nothing to stop a site calling webkitRequestFullScreen() on an
element when another element is fullscreened (though I don't know what the
intended behavoiur is in that case...)

+    return;
+  ToggleFullscreenMode();
+}
+
+void Browser::ExitFullscreenMode() {
+  if (!window_->IsFullscreen())

[scherkus (not reviewing), 2011/07/28 22:43:08]

ditto

[koz (OOO until 15th September), 2011/07/29 04:12:58]

As above.

+    return;
+  ToggleFullscreenMode();
+}
+
 ///////////////////////////////////////////////////////////////////////////////
 // Browser, TabContentsWrapperDelegate implementation: