Add `frame_ancestor_relation` to `net::IsolationInfo` This change adds a new field to `net::IsolationInfo` called `frame_ancestor_relation`, which is primarily calculated in `RenderFrameHostImpl::ComputeIsolationInfoInternal`, similar to `net::SiteForCookies`. This tracks the relationship between a a request and all of its frame's ancestors which will allow us to add a new `Sec-Fetch-Frame-Ancestors` header in a follow-up CL: http://crrev.com/c/6523763 This patch was originally drafted by sledoux@chromium.org (@sjledoux on GitHub): http://crrev.com/c/6199199 Bug: 398224102 Change-Id: I5d3ab9cfbfba1f68ebae8ee2959a55bbe6b10394 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6499507 Reviewed-by: Giovanni Ortuno Urquidi <ortuno@chromium.org> Reviewed-by: Chris Fredrickson <cfredric@chromium.org> Reviewed-by: mmenke <mmenke@chromium.org> Commit-Queue: Joshua Thomas <masnoble@chromium.org> Cr-Commit-Position: refs/heads/main@{#1466645}
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.