commit | cc91f92254205da299b1d67d78beb6cbcfff25f9 | [log] [tgz] |
---|---|---|
author | Ari Chivukula <[email protected]> | Wed Aug 21 14:44:51 2024 |
committer | Chromium LUCI CQ <[email protected]> | Wed Aug 21 14:44:51 2024 |
tree | 9832040c0a7676a42d1b4f9f7f0f8df0f1c751a3 | |
parent | e2cc498338d69a1a54270faaa92590924d1b5b30 [diff] |
[Partitioned Popins] (4) Renderer popin (top-)site(-for-cookies) This CL implements the barest knowledge the renderer should need to have of whether it represents a partitioned popin. This knowledge is necessary to ensure proper checks for data access, like the cookies tested here, are possible. This series of CLs implement core components of the Partitioned Popin system, significant additional effort will be needed to align with the explainer and I2P, but all of that will depend on this work: (1) Implement `popin` window feature (2) `popin` feature triggers tab modal popup (3) `popin` feature triggers third-party storage partitioning (4) Renderer awareness of popin top-origin (5) Limit window.opener access for popin (6) Add permissions policy for popin Explainer: https://explainers-by-googlers.github.io/partitioned-popins/ I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/ApU_zUmpQ2g/ Bug: 340606651 Change-Id: I036c08c2be0f7b8a315b1b517ddbdd3cb72927a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5797543 Reviewed-by: Daniel Cheng <[email protected]> Reviewed-by: Dave Tapuska <[email protected]> Reviewed-by: Rebekah Potter <[email protected]> Auto-Submit: Ari Chivukula <[email protected]> Reviewed-by: Reilly Grant <[email protected]> Commit-Queue: Dave Tapuska <[email protected]> Cr-Commit-Position: refs/heads/main@{#1344788}
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.