Add a browser test for access control for file: scheme

chrome/test/base/in_process_browser_test.cc

Index: chrome/test/base/in_process_browser_test.cc
diff --git a/chrome/test/base/in_process_browser_test.cc b/chrome/test/base/in_process_browser_test.cc
index 73c2156714d0a9508faf0360fe7aed91ccb23e8d..2f05f668a490bc1563ed31451a4e6588ac23cc0c 100644
--- a/chrome/test/base/in_process_browser_test.cc
+++ b/chrome/test/base/in_process_browser_test.cc
@@ -27,6 +27,7 @@
 #include "chrome/browser/devtools/devtools_window.h"
 #include "chrome/browser/lifetime/application_lifetime.h"
 #include "chrome/browser/lifetime/termination_notification.h"
+#include "chrome/browser/net/chrome_network_delegate.h"
 #include "chrome/browser/net/net_error_tab_helper.h"
 #include "chrome/browser/profiles/profile.h"
 #include "chrome/browser/profiles/profile_manager.h"
@@ -255,6 +256,9 @@ void InProcessBrowserTest::SetUp() {
   // Polymer Elements are used for quick unlock configuration in options page,
   // which is chromeos specific feature.
   options::BrowserOptionsHandler::DisablePolymerPreloadForTesting();
+  // browser_tests and interactive_ui_tests rely on the ability to open any
+  // files via file: scheme.
+  ChromeNetworkDelegate::EnableAccessToAllFilesForTesting(true);
 #endif  // defined(OS_CHROMEOS)
 
   // Use hardcoded quota settings to have a consistent testing environment.