PlzNavigate: make MHTML iframe load working.

content/common/navigation_params_unittest.cc

Index: content/common/navigation_params_unittest.cc
diff --git a/content/common/navigation_params_unittest.cc b/content/common/navigation_params_unittest.cc
index ee1f96a68e0f890529f18b60a8a4e1254bffa109..0fdadef61ea4d4aa06ed0dd344a13827ee4ef9cf 100644
--- a/content/common/navigation_params_unittest.cc
+++ b/content/common/navigation_params_unittest.cc
@@ -17,11 +17,11 @@ TEST(NavigationParamsTest, ShouldMakeNetworkRequestForURL) {
   EXPECT_TRUE(ShouldMakeNetworkRequestForURL(GURL("http://foo/bar.html")));
   EXPECT_TRUE(ShouldMakeNetworkRequestForURL(GURL("https://foo/bar.html")));
   EXPECT_TRUE(ShouldMakeNetworkRequestForURL(GURL("data://foo")));
+  EXPECT_TRUE(ShouldMakeNetworkRequestForURL(GURL("cid:foo@bar")));

[carlosk, 2017/05/03 16:56:49]

nit: Please add a comment explaining why cid: and data: URLs should return
|true| here even though they don't actually generate actual network requests.
It could be something in the lines of: "Even though data: and cid: schemes do
not generate actual network requests they must be handled by the network stack
and so must return true for this check."

[arthursonzogni, 2017/05/04 14:26:32]

Yes, really good idea, especially for "data:".
Done.

 
   EXPECT_FALSE(ShouldMakeNetworkRequestForURL(GURL("about:blank")));
   EXPECT_FALSE(ShouldMakeNetworkRequestForURL(GURL("about:srcdoc")));
   EXPECT_FALSE(ShouldMakeNetworkRequestForURL(GURL("javascript://foo.js")));
-  EXPECT_FALSE(ShouldMakeNetworkRequestForURL(GURL("cid:foo@bar")));
   EXPECT_FALSE(ShouldMakeNetworkRequestForURL(GURL()));
 }