Fix for WebView accessible resources.

chrome/browser/apps/guest_view/web_view_browsertest.cc

Index: chrome/browser/apps/guest_view/web_view_browsertest.cc
diff --git a/chrome/browser/apps/guest_view/web_view_browsertest.cc b/chrome/browser/apps/guest_view/web_view_browsertest.cc
index 2f9a1eb464c8e4cbf75bb1b525945e73f7462415..fb8bb8ea833a80f14f24f482e8a78cb2d3f32967 100644
--- a/chrome/browser/apps/guest_view/web_view_browsertest.cc
+++ b/chrome/browser/apps/guest_view/web_view_browsertest.cc
@@ -2520,6 +2520,13 @@ IN_PROC_BROWSER_TEST_F(WebViewTest,
              "web_view/shim", NEEDS_TEST_SERVER);
 }
 
+// Tests that a WebView accessible resource can actually be loaded from a
+// webpage in a WebView.
+IN_PROC_BROWSER_TEST_F(WebViewTest, LoadWebviewAccessibleResource) {
+  TestHelper("testLoadWebviewAccessibleResource",
+             "web_view/load_webview_accessible_resource", NEEDS_TEST_SERVER);
+}
+
 #if defined(USE_AURA)
 // TODO(wjmaclean): when WebViewTest is re-enabled on the site-isolation
 // bots, then re-enable this test class as well.