Share schemes needed for mixed content checking between the browser and renderer.

chrome/renderer/chrome_content_renderer_client.cc

Index: chrome/renderer/chrome_content_renderer_client.cc
diff --git a/chrome/renderer/chrome_content_renderer_client.cc b/chrome/renderer/chrome_content_renderer_client.cc
index 25add397dcf6f421fde04f5141519bbd39687819..0dcd868d5efc0388351da1d60f2dd6af1562b892 100644
--- a/chrome/renderer/chrome_content_renderer_client.cc
+++ b/chrome/renderer/chrome_content_renderer_client.cc
@@ -396,16 +396,9 @@ void ChromeContentRendererClient::RenderThreadStarted() {
   // TODO(nyquist): Add test to ensure this happens when the flag is set.
   WebSecurityPolicy::registerURLSchemeAsDisplayIsolated(dom_distiller_scheme);
 
-#if defined(OS_CHROMEOS)
-  WebSecurityPolicy::registerURLSchemeAsLocal(
-      WebString::fromUTF8(content::kExternalFileScheme));
-#endif
-
 #if defined(OS_ANDROID)
   WebSecurityPolicy::registerURLSchemeAsAllowedForReferrer(
       WebString::fromUTF8(chrome::kAndroidAppScheme));
-  WebSecurityPolicy::registerURLSchemeAsLocal(
-      WebString::fromUTF8(url::kContentScheme));
 #endif
 
   // chrome-search: pages should not be accessible by bookmarklets
@@ -413,10 +406,6 @@ void ChromeContentRendererClient::RenderThreadStarted() {
   WebSecurityPolicy::registerURLSchemeAsNotAllowingJavascriptURLs(
       chrome_search_scheme);
 
-  // chrome-search: resources shouldn't trigger insecure content warnings. Note
-  // that the chrome-extension: scheme is registered by extensions::Dispatcher.
-  WebSecurityPolicy::registerURLSchemeAsSecure(chrome_search_scheme);
-
 #if BUILDFLAG(ENABLE_PRINT_PREVIEW)
   pdf_print_client_.reset(new ChromePDFPrintClient());
   pdf::PepperPDFHost::SetPrintClient(pdf_print_client_.get());