MD WebUI: Remove WebUI test focus hack by moving to interactive ui tests

chrome/test/base/web_ui_browser_test.cc

Index: chrome/test/base/web_ui_browser_test.cc
diff --git a/chrome/test/base/web_ui_browser_test.cc b/chrome/test/base/web_ui_browser_test.cc
index c50a43458e417ea7807b06f0105ac1e20acec35d..4c8d5bc7c8ad02b2d21baf452880de543058013c 100644
--- a/chrome/test/base/web_ui_browser_test.cc
+++ b/chrome/test/base/web_ui_browser_test.cc
@@ -224,16 +224,6 @@ void WebUIBrowserTest::BrowsePreload(const GURL& browse_to) {
       browser(), GURL(browse_to), ui::PAGE_TRANSITION_TYPED);
   params.disposition = WindowOpenDisposition::CURRENT_TAB;
 
-  // This is needed to make the test
-  // MaterialHistoryBrowserTest.HistoryToolbarFocusTest pass on macOS. The test
-  // is fundamentally flawed, since it expects a particular widget to be
-  // focused. Chrome focus semantics are based on the Windows platform, where a
-  // widget cannot be focused without window activation. browser_tests can be
-  // sharded, so there is no way to enforce that a given window is activated.
-  // Focus tests should be interactive_ui_tests, and they should explicitly
-  // activate the window. https://crbug.com/642467.
-  params.window_action = chrome::NavigateParams::SHOW_WINDOW;
-
   chrome::Navigate(&params);
   navigation_observer.Wait();
 }