Disable flaky LookUpStringForRangeRoutesToFocusedWidget

chrome/browser/renderer_host/site_per_process_text_input_browsertest.cc

Index: chrome/browser/renderer_host/site_per_process_text_input_browsertest.cc
diff --git a/chrome/browser/renderer_host/site_per_process_text_input_browsertest.cc b/chrome/browser/renderer_host/site_per_process_text_input_browsertest.cc
index 18c5e463f8256b2e0ff279041169395b5a284b0f..a06446b7ac41606c3d191efc851e72b01f240e52 100644
--- a/chrome/browser/renderer_host/site_per_process_text_input_browsertest.cc
+++ b/chrome/browser/renderer_host/site_per_process_text_input_browsertest.cc
@@ -1283,8 +1283,9 @@ class TestBrowserClient : public ChromeContentBrowserClient {
 
 // This test verifies that requests for dictionary lookup based on selection
 // range are routed to the focused RenderWidgetHost.
+// Test is flaky: http://crbug.com/710842
 IN_PROC_BROWSER_TEST_F(SitePerProcessTextInputManagerTest,
-                       LookUpStringForRangeRoutesToFocusedWidget) {
+                       DISABLED_LookUpStringForRangeRoutesToFocusedWidget) {
   // TestBrowserClient needs to replace the ChromeContenBrowserClient after most
   // things are initialized but before the WebContents is created. Here we make
   // that happen by creating a new WebContents in a new tab. But before the test