commit | 0e16ab79c7fd3457f957e89ab805952b3868034c | [log] [tgz] |
---|---|---|
author | Ari Chivukula <arichiv@chromium.org> | Thu Nov 02 16:31:10 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 02 16:31:10 2023 |
tree | 6137eea85374451dfdc5bdf01ee15bc180cd71e7 | |
parent | 8e7fbf5cb0099de6bcbc1f2e7463f37c483ef2ba [diff] |
[SAA] Prototyping non-cookie extension (Part 5: origin private file system) The Storage Access API provides access to unpartitioned cookies in third-party contexts. This CL is part of a series to extend that access to non-cookie storage/communication mechanisms. This CL only includes OPFS as a next step for the new access. We want to be deliberate adding new mechanisms since we need good testing and security review here. All access is restricted to experimental contexts for now, no stable access or origin trial timeline has been published. Explainer: https://arichiv.github.io/saa-non-cookie-storage/ Intent to Prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/inRN8tI49O0 Part 1: local/session storage Part 2: indexeddb Part 3: web locks Part 4: cache storage Part 5: origin private file system Part 6: quota Part 7: blob storage Part 8: broadcast channel Part 9: shared worker Bug: 1484966 Change-Id: I17dea8ad85216ab31780cbd277190636c3b71305 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4998167 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Sun Yueru <yrsun@chromium.org> Auto-Submit: Ari Chivukula <arichiv@chromium.org> Reviewed-by: Chris Fredrickson <cfredric@chromium.org> Commit-Queue: Ari Chivukula <arichiv@chromium.org> Cr-Commit-Position: refs/heads/main@{#1218883}
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.