Add Keyboard Latency UMA Metrics.

content/browser/renderer_host/render_widget_host_unittest.cc

Index: content/browser/renderer_host/render_widget_host_unittest.cc
diff --git a/content/browser/renderer_host/render_widget_host_unittest.cc b/content/browser/renderer_host/render_widget_host_unittest.cc
index 2b146c051b536542cd04b89f2bd00dfae6ac43f9..34898f2f6ef6ae8ff1c3727f1004cf1cfa1e3eb7 100644
--- a/content/browser/renderer_host/render_widget_host_unittest.cc
+++ b/content/browser/renderer_host/render_widget_host_unittest.cc
@@ -630,7 +630,7 @@ class RenderWidgetHostTest : public testing::Test {
   void SimulateKeyboardEvent(WebInputEvent::Type type, int modifiers) {
     NativeWebKeyboardEvent native_event(type, modifiers,
                                         GetNextSimulatedEventTimeSeconds());
-    host_->ForwardKeyboardEvent(native_event);
+    host_->ForwardKeyboardEventWithLatencyInfo(native_event, ui::LatencyInfo());

[mfomitchev, 2017/05/10 16:06:09]

Just call ForwardkeyboardEvent() here rather than construct a dummy latency? I
guess doesn't matter much for unit test, but seems better unless there's a
reason not to.

[tdresser, 2017/05/10 19:31:50]

Sorry, missed this case.
Done.

   }
 
   void SimulateKeyboardEventWithCommands(WebInputEvent::Type type) {
@@ -638,7 +638,8 @@ class RenderWidgetHostTest : public testing::Test {
                                         GetNextSimulatedEventTimeSeconds());
     EditCommands commands;
     commands.emplace_back("name", "value");
-    host_->ForwardKeyboardEventWithCommands(native_event, &commands, nullptr);
+    host_->ForwardKeyboardEventWithCommands(native_event, ui::LatencyInfo(),
+                                            &commands, nullptr);
   }
 
   void SimulateMouseEvent(WebInputEvent::Type type) {