Handle initial empty document for SiteInstanceGroup and RenderDocument Before SiteInstanceGroup with RenderDocument enabled, for same-site navigations, the initial empty document would always be reused. With SiteInstanceGroup, that's still true, but the function used to check that, ShouldCreateRenderFrameHostForSameSiteNavigation, was being called for same-SiteInstanceGroup but cross-SiteInstance navigations. The function is only valid for same-SiteInstance navigations. Update the callers to enforce this and add a comment to clarify this function only works for same-site navigations. Test: SitePerProcessNotIsolatedSandboxedIframeTest Change-Id: I13ac26524a9d36ddf86f405d6f29ecc2817227ea Bug: 40269084, 40615943 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5906885 Reviewed-by: Rakina Zata Amni <rakina@chromium.org> Commit-Queue: Sharon Yang <yangsharon@chromium.org> Cr-Commit-Position: refs/heads/main@{#1381056}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.