Support parsing BackgroundSpans and UnderlineSpans in Android IME's commitText()

content/common/input_messages.h

 // Copyright (c) 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 input events and other messages that require processing in
 // order relative to input events.
 // Multiply-included message file, hence no include guard.
 
 #include "base/strings/string16.h"
 #include "build/build_config.h"
@@ skipping 154 matching lines @@
 IPC_MESSAGE_ROUTED5(
     InputMsg_ImeSetComposition,
     base::string16, /* text */
     std::vector<blink::WebCompositionUnderline>, /* underlines */
     gfx::Range /* replacement_range */,
     int, /* selectiont_start */
     int /* selection_end */)
 
 // This message deletes the current composition, inserts specified text, and
 // moves the cursor.
-IPC_MESSAGE_ROUTED3(InputMsg_ImeCommitText,
-                    base::string16 /* text */,
-                    gfx::Range /* replacement_range */,
-                    int /* relative_cursor_pos */)
+IPC_MESSAGE_ROUTED4(
+    InputMsg_ImeCommitText,
+    base::string16 /* text */,
+    std::vector<blink::WebCompositionUnderline>, /* underlines */
+    gfx::Range /* replacement_range */,
+    int /* relative_cursor_pos */)
 
 // This message inserts the ongoing composition.
 IPC_MESSAGE_ROUTED1(InputMsg_ImeFinishComposingText, bool /* keep_selection */)
 
 // This message notifies the renderer that the next key event is bound to one
 // or more pre-defined edit commands. If the next key event is not handled
 // by webkit, the specified edit commands shall be executed against current
 // focused frame.
 // Parameters
 // * edit_commands (see chrome/common/edit_command_types.h)
@@ skipping 120 matching lines @@
 // This IPC message sends the character bounds after every composition change
 // to always have correct bound info.
 IPC_MESSAGE_ROUTED2(InputHostMsg_ImeCompositionRangeChanged,
                     gfx::Range /* composition range */,
                     std::vector<gfx::Rect> /* character bounds */)
 
 // Adding a new message? Stick to the sort order above: first platform
 // independent InputMsg, then ifdefs for platform specific InputMsg, then
 // platform independent InputHostMsg, then ifdefs for platform specific
 // InputHostMsg.