Skip to content
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.

Update auto-deny and auto-grant behavior in RWS #7713

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Update auto-deny and auto-grant behavior in RWS #7713

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion site/en/docs/privacy-sandbox/related-website-sets-integration/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,9 @@ The [Storage Access API (SAA)](https://privacycg.github.io/storage-access/) prov

Embedded resources can use SAA methods to check whether they currently have access to storage, and to request access from the user agent.

When third-party cookies are blocked, but Related Website Sets are allowed, Chrome will automatically grant that permission for sites within the set and deny it for sites outside the set.
When third-party cookies are blocked, but Related Website Sets are allowed, Chrome will automatically grant that permission for sites within the set and deny it for sites outside the set. But Chrome won't auto-deny permissions to all sites that aren't in a RWS; that's only true before we've shipped the full SAA w/ prompts feature.

Furthermore, Chrome only auto-grants permissions to RWS sites if they're embedded under another site in the same Related Website Set.

{% Aside %}
SAA is shipping in several browsers, however there are [differences between browser implementations](https://developer.mozilla.org/docs/Web/API/Storage_Access_API#safari_implementation_differences) in the rules of handling storage access.
Expand Down
Loading