Browser Side Text Input State Tracking for OOPIF.

content/browser/browser_plugin/browser_plugin_guest.cc

Index: content/browser/browser_plugin/browser_plugin_guest.cc
diff --git a/content/browser/browser_plugin/browser_plugin_guest.cc b/content/browser/browser_plugin/browser_plugin_guest.cc
index fd0c173ed0b97c250546934846d0ac482e19d88b..ad4474faea1ef7df997a2cf7daede72c105c3187 100644
--- a/content/browser/browser_plugin/browser_plugin_guest.cc
+++ b/content/browser/browser_plugin/browser_plugin_guest.cc
@@ -979,10 +979,9 @@ void BrowserPluginGuest::OnTakeFocus(bool reverse) {
       new BrowserPluginMsg_AdvanceFocus(browser_plugin_instance_id(), reverse));
 }
 
-void BrowserPluginGuest::OnTextInputStateChanged(
-    const ViewHostMsg_TextInputState_Params& params) {
+void BrowserPluginGuest::OnTextInputStateChanged(const TextInputState& params) {
   // Save the state of text input so we can restore it on focus.
-  last_text_input_state_.reset(new ViewHostMsg_TextInputState_Params(params));
+  last_text_input_state_.reset(new TextInputState(params));
 
   SendTextInputTypeChangedToView(

[lazyboy, 2016/04/04 19:17:59]

(As discussed offline): maybe we can go to web_contents() directly instead of
through view. Sadly, we might still need to store |last_text_input_state_|

[EhsanK, 2016/04/06 00:37:58]

Yes. I will try to fix it in a follow-up CL.

       static_cast<RenderWidgetHostViewBase*>(