Chrome 141/Firefox 140 storage access activation per origin #28682
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
While using the Storage Access API, when embedded content activates a previously-granted
storage-accesspermission via therequestStorageAccess()method, 3rd party cookies are now only sent with requests to the calling embed's exact origin.Previously, 3rd party cookies were sent with requests to the calling embed's site.
This behavioral change has occurred in:
This PR adds notes in relevant places to document this change.
cc @cfredric / @hamishwillee — I'd appreciate your input on this one, folks.
Test results and supporting details
Related issues