Hide location bar on Javascript-initiated scroll.

content/common/view_messages.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // IPC messages for page rendering.
 // Multiply-included message file, hence no include guard.
 
 #include "base/process.h"
 #include "base/shared_memory.h"
 #include "base/string16.h"
@@ skipping 1348 matching lines @@
 IPC_MESSAGE_ROUTED1(ViewMsg_ImeBatchStateChanged,
     bool /* is_begin */)
 
 // Notifies the renderer whether hiding/showing the top controls is enabled
 // and whether or not to animate to the proper state.
 IPC_MESSAGE_ROUTED3(ViewMsg_UpdateTopControlsState,
                     bool /* enable_hiding */,
                     bool /* enable_showing */,
                     bool /* animate */)
 
+// Tells the renderer to show or hide the top controls.
+IPC_MESSAGE_ROUTED1(ViewMsg_ShowTopControls, bool /* show */)

[jam, 2013/04/17 16:24:59]

i'm not familiar what top controls are?

is this a ui feature of the android browser?

[Michael van Ouwerkerk, 2013/04/18 18:11:38]

It's the piece of browser ui at the top that includes the url bar, tab switching
button, menu button, etc. It gets hidden in fullscreen mode.

Related code: cc/input/top_controls_manager.h

[jam, 2013/04/19 18:30:22]

I see. it seems like a layering violation that this code (anything related to
top controls) is in content, since content just knows about rendering a view.
anything related to the UI of an app is the responsibility of the embedder.

+
 IPC_MESSAGE_ROUTED0(ViewMsg_ShowImeIfNeeded)
 
 #elif defined(OS_MACOSX)
 // Let the RenderView know its window has changed visibility.
 IPC_MESSAGE_ROUTED1(ViewMsg_SetWindowVisibility,
                     bool /* visibile */)
 
 // Let the RenderView know its window's frame has changed.
 IPC_MESSAGE_ROUTED2(ViewMsg_WindowFrameChanged,
                     gfx::Rect /* window frame */,
@@ skipping 122 matching lines @@
 // Send in response to a ViewMsg_UpdateScreenRects so that the renderer can
 // throttle these messages.
 IPC_MESSAGE_ROUTED0(ViewHostMsg_UpdateScreenRects_ACK)
 
 // Sent by the renderer process to request that the browser move the view.
 // This corresponds to the window.resizeTo() and window.moveTo() APIs, and
 // the browser may ignore this message.
 IPC_MESSAGE_ROUTED1(ViewHostMsg_RequestMove,
                     gfx::Rect /* position */)
 
+// Sent by the renderer process to notify the browser that the web page has
+// programmatically scrolled.
+IPC_MESSAGE_ROUTED1(ViewHostMsg_DidProgrammaticallyScroll,
+                    gfx::Point /* scroll point */)

[jam, 2013/04/17 16:24:59]

nit: convention is that the comment holds the parameter name in the dispatching
method, i.e. scroll_point

[Michael van Ouwerkerk, 2013/04/18 18:11:38]

Done.

+
 // Notifies the browser that a frame in the view has changed. This message
 // has a lot of parameters and is packed/unpacked by functions defined in
 // render_messages.h.
 IPC_MESSAGE_ROUTED1(ViewHostMsg_FrameNavigate,
                     ViewHostMsg_FrameNavigate_Params)
 
 // Used to tell the parent that the user right clicked on an area of the
 // content area, and a context menu should be shown for it. The params
 // object contains information about the node(s) that were selected when the
 // user right clicked.
@@ skipping 879 matching lines @@
 // cached by the OS. Please see RenderMessageFilter::OnPreCacheFontCharacters
 // for details.
 IPC_SYNC_MESSAGE_CONTROL2_0(ViewHostMsg_PreCacheFontCharacters,
                             LOGFONT /* font_data */,
                             string16 /* characters */)
 #endif
 
 // Adding a new message? Stick to the sort order above: first platform
 // independent ViewMsg, then ifdefs for platform specific ViewMsg, then platform
 // independent ViewHostMsg, then ifdefs for platform specific ViewHostMsg.