Use mojo for Chrome Loading, Part 1

third_party/WebKit/LayoutTests/VirtualTestSuites

Index: third_party/WebKit/LayoutTests/VirtualTestSuites
diff --git a/third_party/WebKit/LayoutTests/VirtualTestSuites b/third_party/WebKit/LayoutTests/VirtualTestSuites
index 90d2366e0b25e2c2fd32eee6ab04e2c8714dbeab..c29a518c3ff7e34146a39daedafec649786088c3 100644
--- a/third_party/WebKit/LayoutTests/VirtualTestSuites
+++ b/third_party/WebKit/LayoutTests/VirtualTestSuites
@@ -252,5 +252,10 @@
     "prefix": "documentwriteevaluator",
     "base": "http/tests/preload/document-write",
     "args": ["--enable-blink-features=DocumentWriteEvaluator"]
+  },
+  {
+    "prefix": "mojo-loading",
+    "base": "webexposed",

[kinuko, 2016/05/20 09:38:51]

Why webexposed? Does the directory have interesting basic loading tests??

[yhirano, 2016/05/20 11:32:54]

It's important that they are not interesting. Mojo is used when html files are
fetched, and that's what I want to test for this change.

[kinuko, 2016/05/20 15:56:46]

Oh I see... (I wish we could have a comment to note that in this file... but
it's json and maybe we can't)

[yhirano, 2016/05/23 11:29:37]

Added a comment in README.txt.

+    "args": ["--enable-blink-features=LoadingWithMojo"]
   }
 ]