Block webpages from navigating to view-source URLs

content/browser/web_contents/web_contents_impl_browsertest.cc

Index: content/browser/web_contents/web_contents_impl_browsertest.cc
diff --git a/content/browser/web_contents/web_contents_impl_browsertest.cc b/content/browser/web_contents/web_contents_impl_browsertest.cc
index 55e00c56a3ffd08c3d3b1d99be653b83ba2fa5e5..2aa8f5706db93d3cd255fe33f8a2b9b1f3325d8c 100644
--- a/content/browser/web_contents/web_contents_impl_browsertest.cc
+++ b/content/browser/web_contents/web_contents_impl_browsertest.cc
@@ -770,6 +770,14 @@ IN_PROC_BROWSER_TEST_F(WebContentsImplBrowserTest, ChangePageScale) {
   observer.WaitForPageScaleUpdate();
 }
 
+// Test view source mode for a webui page.
+IN_PROC_BROWSER_TEST_F(WebContentsImplBrowserTest, WebUIViewSource) {

[Charlie Reis, 2016/05/16 22:22:18]

Seems like a nice test.  Was this behavior at risk in one of your attempts, or
is this more of a general sanity check that we can do browser-initiated
view-source for WebUI?

[meacer, 2016/05/19 01:13:54]

I didn't run into this case in my attempts, but I got the idea from
WebContentsImplTest.ContentInitiatedViewSource test. I fixed the other test now,
but it seemed fragile because it manually constructed the URL to be navigated
to.

+  const char kUrl[] = "view-source:chrome://chrome/settings";
+  const GURL kGURL(kUrl);
+  NavigateToURL(shell(), kGURL);
+  EXPECT_EQ(base::ASCIIToUTF16(kUrl), shell()->web_contents()->GetTitle());
+}
+
 IN_PROC_BROWSER_TEST_F(WebContentsImplBrowserTest, NewNamedWindow) {
   ASSERT_TRUE(embedded_test_server()->Start());