Ensure that the OSK on Windows 8 shows up when we tap on an editable field in any WebContents.

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/memory/shared_memory.h"
 #include "base/process/process.h"
 #include "base/strings/string16.h"
@@ skipping 2244 matching lines @@
 
 // Sent by the renderer to the browser to start a vibration with the given
 // duration.
 IPC_MESSAGE_CONTROL1(ViewHostMsg_Vibrate,
                      int64 /* milliseconds */)
 
 // Sent by the renderer to the browser to cancel the currently running
 // vibration, if there is one.
 IPC_MESSAGE_CONTROL0(ViewHostMsg_CancelVibration)
 
+// Message sent from renderer to the browser when the element that is focused
+// has been touched. A bool is passed in this message which indicates if the
+// node is editable.
+IPC_MESSAGE_ROUTED1(ViewHostMsg_FocusedNodeTouched,
+                    bool /* editable */)
+
 #if defined(OS_ANDROID)
 // Response to ViewMsg_FindMatchRects.
 //
 // |version| will contain the current version number of the renderer's find
 // match list (incremented whenever they change), which should be passed in the
 // next call to ViewMsg_FindMatchRects.
 //
 // |rects| will either contain a list of the enclosing rects of all matches
 // found by the most recent Find operation, or will be empty if |version| is not
 // greater than the |current_version| passed to ViewMsg_FindMatchRects (hence
@@ skipping 79 matching lines @@
 // synchronously (see crbug.com/120597). This IPC message sends the character
 // bounds after every composition change to always have correct bound info.
 IPC_MESSAGE_ROUTED2(ViewHostMsg_ImeCompositionRangeChanged,
                     gfx::Range /* composition range */,
                     std::vector<gfx::Rect> /* character bounds */)
 #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.