Implement `fenced-frame-unparititioned-data` Permissions Policy The default value for this permission is *. Regarding testing: The existing permissions_policy.js test framework relies on postMessage() to send test results out of the frame. Fenced frames do not have access to postMessage(), by design. I rolled my own test helper using RemoteContext instead. Change-Id: Ieb8184dafd0dc4281c0375b0141c012cb0f0f793 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5920994 Commit-Queue: Andrew Verge <averge@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Reviewed-by: Liam Brady <lbrady@google.com> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/main@{#1371476}
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.