Mandoline: Support about:blank URL.

mojo/runner/context.cc

Index: mojo/runner/context.cc
diff --git a/mojo/runner/context.cc b/mojo/runner/context.cc
index 7a6a6adf19b303f6139289676ddd933b3be7b087..31632995f28826f4c610332108d0162c5e0cc15e 100644
--- a/mojo/runner/context.cc
+++ b/mojo/runner/context.cc
@@ -29,6 +29,7 @@
 #include "mojo/common/tracing_impl.h"
 #include "mojo/edk/embedder/embedder.h"
 #include "mojo/edk/embedder/simple_platform_support.h"
+#include "mojo/runner/about_fetcher.h"
 #include "mojo/runner/in_process_native_runner.h"
 #include "mojo/runner/out_of_process_native_runner.h"
 #include "mojo/runner/switches.h"
@@ -337,6 +338,11 @@ GURL Context::ResolveMojoURL(const GURL& url) {
 bool Context::CreateFetcher(
     const GURL& url,
     const shell::Fetcher::FetchCallback& loader_callback) {
+  if (url.SchemeIs(AboutFetcher::kAboutScheme)) {
+    new AboutFetcher(url, loader_callback);

[sky, 2015/08/04 20:04:56]

Document AboutFetcher deletes itself. Also, do we always want this behavior? By
that I mean we definitely want to support about:blank, but it's not clear that
about:blank should always be text/html.

[yzshen1, 2015/08/05 16:11:08]

Done.
In what cases about:blank shouldn't be text/html?
I am not sure I understand. Do you mean we need more than one way to handle
about:blank?

Or do you mean we need different behavior for other "about:" URLs? That is
possible. We could have different MIME types or register different applications
for different "about:" URLs.

+    return true;
+  }
+
   return false;
 }