Remove about:srcdoc url conversion.

content/browser/site_instance_impl.cc

Index: content/browser/site_instance_impl.cc
diff --git a/content/browser/site_instance_impl.cc b/content/browser/site_instance_impl.cc
index 7980783a7d3ed0acfe3da00d14a192471abd8e75..83547cd7748094d1388fab96fb516e939d2d8da1 100644
--- a/content/browser/site_instance_impl.cc
+++ b/content/browser/site_instance_impl.cc
@@ -316,10 +316,9 @@ bool SiteInstance::IsSameWebSite(BrowserContext* browser_context,
   if (!src_url.is_valid() || !dest_url.is_valid())
     return false;
 
-  // If the destination url is just a blank page, we treat them as part of the
-  // same site.
-  GURL blank_page(url::kAboutBlankURL);
-  if (dest_url == blank_page)
+  // If the destination url is just about:blank or about:srcdoc, we treat them
+  // as part of the same site.
+  if (dest_url == url::kAboutBlankURL || dest_url == content::kAboutSrcDocURL)

[Charlie Reis, 2016/11/22 01:01:20]

Let's leave this out.  As I mentioned in a previous patchset, I think we're
already doing the right thing by letting RFHM handle it, and I worry that this
could introduce a problem.  (For example, if a parent frame tells an OOPIF to go
to a srcdoc, it should join the parent's process and not stay in whatever
process it was in before.)

[arthursonzogni, 2016/11/22 16:43:27]

I add a test in a separate CL:
https://codereview.chromium.org/2525433003/

FYI: the test passes with this CL. But I will still remove this part in case
there are other problems.

     return true;
 
   // If the schemes differ, they aren't part of the same site.