Block webpages from navigating to view-source URLs

content/renderer/render_thread_impl.cc

Index: content/renderer/render_thread_impl.cc
diff --git a/content/renderer/render_thread_impl.cc b/content/renderer/render_thread_impl.cc
index 98cf865b75a289b5fca64e2702727de44238a902..9a4ce5a1648a1ee7a042a2428b4a736064de2702 100644
--- a/content/renderer/render_thread_impl.cc
+++ b/content/renderer/render_thread_impl.cc
@@ -1325,6 +1325,10 @@ void RenderThreadImpl::RegisterSchemes() {
   // chrome-devtools:
   WebString devtools_scheme(base::ASCIIToUTF16(kChromeDevToolsScheme));
   WebSecurityPolicy::registerURLSchemeAsDisplayIsolated(devtools_scheme);
+
+  // view-source:
+  WebString view_source_scheme(base::ASCIIToUTF16(kViewSourceScheme));
+  WebSecurityPolicy::registerURLSchemeAsDisplayIsolated(view_source_scheme);

[Charlie Reis, 2016/04/27 21:47:03]

This seems to equate to SecurityOrigin::canDisplay, which has the following
comment:
    // Returns true if |document| can display content from the given URL (e.g.,
    // in an iframe or as an image). For example, web sites generally cannot
    // display content from the user's files system.

Does it also prevent linking or navigating to such content?  I don't see the
code for that.

[meacer, 2016/05/12 01:14:16]

Yes, it also prevents linking and navigation. I think |canDisplay| is a misnomer
and we should probably consider renaming it and updating its documentation.

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

Ah.  Yes, that would be a good idea.  Do you know which code prevents linking
and navigation for those schemes?  I couldn't find it.  (I can ask dcheng@ if
not.)

 }
 
 void RenderThreadImpl::NotifyTimezoneChange() {