Fenced frames: Disable Open Link in Profile context menu options when network is revoked. Fenced frames(FF) can disable network access by invoking FF API: window.fence.disableUntrustedNetwork(). After the network access is revoked, FF will get access to cross-site data, for example, via shared storage get API. The principle is no network request can be made using URLs in a network-disabled FF, including user triggered main-frame navigations. This is because the URL can leak cross-site data, for example, by appending the cross-site data to the URL. This CL disables Open Link in Profile context menu options when FF network is revoked. Bug: 364906214 Change-Id: I12de18f757f7fb5d04c7b820ed9cfd62430d94de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5933688 Reviewed-by: Avi Drissman <avi@chromium.org> Commit-Queue: Xiaochen Zhou <xiaochenzh@chromium.org> Reviewed-by: Ryan Sultanem <rsult@google.com> Cr-Commit-Position: refs/heads/main@{#1375783}
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.