[Android] Adding Smart GO/NEXT feature in Chrome

content/common/frame_messages.h

 // Copyright 2013 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 interacting with frames.
 // Multiply-included message file, hence no include guard.
 
 #include <stddef.h>
 #include <stdint.h>
 
@@ skipping 965 matching lines @@
                     content::FrameOwnerProperties /* frame_owner_properties */)
 
 // Request to continue running the sequential focus navigation algorithm in
 // this frame.  |source_routing_id| identifies the frame that issued this
 // request.  This message is sent when pressing <tab> or <shift-tab> needs to
 // find the next focusable element in a cross-process frame.
 IPC_MESSAGE_ROUTED2(FrameMsg_AdvanceFocus,
                     blink::WebFocusType /* type */,
                     int32_t /* source_routing_id */)
 
+// Tells the RenderFrame to advance the focus to next input node in the form by
+// moving in specified direction if the currently focused node is a Text node
+// (textfield, text area or content editable nodes).
+IPC_MESSAGE_ROUTED1(FrameMsg_AdvanceFocusInForm,
+                    blink::WebFocusType /* direction for advancing focus */)
+
 // Sent when the user wants to search for a word on the page (find-in-page).
 IPC_MESSAGE_ROUTED3(FrameMsg_Find,
                     int /* request_id */,
                     base::string16 /* search_text */,
                     blink::WebFindOptions)
 
 // This message notifies the frame that it is no longer the active frame in the
 // current find session, and so it should clear its active find match (and no
 // longer highlight it with special coloring).
 IPC_MESSAGE_ROUTED0(FrameMsg_ClearActiveFindMatch)
@@ skipping 695 matching lines @@
                     int /* nfr_request_id */,
                     float /* distance */)
 
 IPC_MESSAGE_ROUTED0(FrameHostMsg_NavigationHandledByEmbedder)
 #endif
 
 // Adding a new message? Stick to the sort order above: first platform
 // independent FrameMsg, then ifdefs for platform specific FrameMsg, then
 // platform independent FrameHostMsg, then ifdefs for platform specific
 // FrameHostMsg.