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

content/renderer/render_view_impl.cc

Index: content/renderer/render_view_impl.cc
diff --git a/content/renderer/render_view_impl.cc b/content/renderer/render_view_impl.cc
index 419a8d09605b012d13531d540301ec587baf37bc..64996aec9ffbd8001df601a6ef17dd5f9045b544 100644
--- a/content/renderer/render_view_impl.cc
+++ b/content/renderer/render_view_impl.cc
@@ -129,6 +129,7 @@
 #include "third_party/WebKit/Source/Platform/chromium/public/WebCString.h"
 #include "third_party/WebKit/Source/Platform/chromium/public/WebDragData.h"
 #include "third_party/WebKit/Source/Platform/chromium/public/WebFileSystemType.h"
+#include "third_party/WebKit/Source/Platform/chromium/public/WebFloatSize.h"
 #include "third_party/WebKit/Source/Platform/chromium/public/WebHTTPBody.h"
 #include "third_party/WebKit/Source/Platform/chromium/public/WebImage.h"
 #include "third_party/WebKit/Source/Platform/chromium/public/WebMessagePortChannel.h"
@@ -2204,6 +2205,11 @@ bool RenderViewImpl::handleCurrentKeyboardEvent() {
   return did_execute_command;
 }
 
+void RenderViewImpl::didScrollWithKeyboard(const WebKit::WebFloatSize& delta) {
+  if (delta.height != 0.f)

[Ted C, 2013/06/03 17:43:42]

Hmm...this behavior isn't really consistent with how touch events are processed.

In the normal touch case, the top controls will consume the portion of the
scroll total before it's applied to the root layer (bringing in or hiding the
top controls before the page content moves).  Here it will not be tied to that
and will happen at the same time.  It might be kind of odd, but I don't know if
there is an easier way of handling that.  I'm also worried that the top controls
will pop in and out if you just toggle up and down a bit.

I wonder if it would be better to send these scroll deltas to the top controls
manager (moving the top controls by the same amount) and have it kick off an
internal timer to animate if no further scrolls are received.

Granted, I don't think most people will have a keyboard attached in the android
world, so this is probably ok.

[Jinsuk Kim, 2013/06/05 08:21:07]

Thanks for spotting it. The transition does look different from that caused by
gesture. Let me try to work on that part (plus animation) in other CL after I
get familiar enough with the codebase.

+    compositor_->ShowTopControls(delta.height < 0.f);
+}
+
 WebKit::WebColorChooser* RenderViewImpl::createColorChooser(
     WebKit::WebColorChooserClient* client,
     const WebKit::WebColor& initial_color) {