Allows fullscreen to be triggered with the key events used for scrolling.

cc/input/top_controls_state.h

Index: cc/input/top_controls_state.h
diff --git a/cc/input/top_controls_state.h b/cc/input/top_controls_state.h
index 87b86c0269194f1ea86e28598b1de67b65d2286d..d685e500914718376985062a0f23cda9ed713056 100644
--- a/cc/input/top_controls_state.h
+++ b/cc/input/top_controls_state.h
@@ -7,6 +7,7 @@
 
 namespace cc {
 enum TopControlsState {
+  INVALID = 0,

[jamesr, 2013/06/13 02:06:59]

I still don't understand this.  TopControlsState is used to define the valid
positions for the top controls - either shown, hidden, or both (it doesn't
matter where they are).  What does another state mean?  If you don't care where
the top controls are, isn't BOTH the correct value?

[aelias_OOO_until_Jul13, 2013/06/13 03:29:25]

This will clobber the existing constraints, I assume that's his concern.  The
value in cc::TopControlsManager can default to BOTH, so if the one in
RenderViewImpl also defaults to BOTH, they'll stay in sync.

[Jinsuk Kim, 2013/06/13 04:18:13]

Thanks for the tip. I found that permitted_state_ is initialized to BOTH, so set
the top_controls_constraints_ to BOTH too.

[Jinsuk Kim, 2013/06/13 04:18:13]

Set to BOTH.

   SHOWN = 1,
   HIDDEN = 2,
   BOTH = 3