Automated tests for full screen & mouse lock M16 features

chrome/browser/ui/fullscreen_controller.h

Index: chrome/browser/ui/fullscreen_controller.h
diff --git a/chrome/browser/ui/fullscreen_controller.h b/chrome/browser/ui/fullscreen_controller.h
index 9af0e7da935ed4fe2cafa61b70df2705773c05e8..f77e3d071ea879350a3e9d0b4fdd8a3c673055b9 100644
--- a/chrome/browser/ui/fullscreen_controller.h
+++ b/chrome/browser/ui/fullscreen_controller.h
@@ -41,9 +41,10 @@ class FullscreenController : public base::RefCounted<FullscreenController> {
   virtual ~FullscreenController();
 
   // Querying.
-  bool IsFullscreenForTab() const;
-  bool IsFullscreenForTab(const content::WebContents* tab) const;
+  bool IsFullscreenForBrowser() const;
+  bool IsFullscreenForTabOrPending() const;

[yzshen1, 2012/03/16 07:33:28]

Nit: Would you please add a comment about what 'pending' means here?
Are we waiting for the user's permission before we can process the fullscreen
request?
Or entering fullscreen is an async operation and it is now in the middle of the
transition?
  

[scheib, 2012/03/16 21:20:03]

Done.

   bool IsFullscreenForTabOrPending(const content::WebContents* tab) const;
+  bool IsMouseLockedOrPending() const;
 
   // Requests.
   void RequestToLockMouse(content::WebContents* tab);