Fix an IME bug where RWHImpl::ImeFinishCompositingText is called twice in a row

content/browser/renderer_host/render_widget_host_view_aura_unittest.cc

Index: content/browser/renderer_host/render_widget_host_view_aura_unittest.cc
diff --git a/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc b/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc
index 6800c342bfa7cfdc26a132af41f112589f57b771..97ff6d25e07dff664c9c988cea17f869f8979707 100644
--- a/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc
+++ b/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc
@@ -1580,13 +1580,10 @@ TEST_F(RenderWidgetHostViewAuraTest, FinishCompositionByMouse) {
 
   EXPECT_EQ(2U, sink_->message_count());
 
-  if (sink_->message_count() == 2) {
-    // Verify mouse event happens after the finish composing text event.
-    EXPECT_EQ(InputMsg_ImeFinishComposingText::ID,
-              sink_->GetMessageAt(0)->type());
-    EXPECT_EQ(InputMsg_HandleInputEvent::ID,
-              sink_->GetMessageAt(1)->type());
-  }
+  // Verify mouse event happens after the finish composing text event.
+  EXPECT_EQ(InputMsg_ImeFinishComposingText::ID,

[sadrul, 2017/05/30 21:03:03]

ASSERT that sink_->message_count() >= 2 before accessing GetMessageAt(0)/1 to
avoid crashes on failure.

[Shu Chen, 2017/05/31 01:16:36]

+1. Can we assert message_count == 2? Or can we check no dup
ImeFinishComposingText?

[EhsanK, 2017/05/31 13:48:24]

Thanks! Changed the EXPECT on line 1581 into ASSERT.

+            sink_->GetMessageAt(0)->type());
+  EXPECT_EQ(InputMsg_HandleInputEvent::ID, sink_->GetMessageAt(1)->type());
 }
 
 // Checks that touch-event state is maintained correctly.