[WIP] Enable get() in fenced frames with network access revoked. #220
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.
After script running in a fenced frame successfully resolves a call to
window.fence.disableUntrustedNetwork()
, the fenced frame gains access to Shared Storage viaget()
.This patch refactors the
get()
algorithm to be accessible fromWindow
andSharedStorageWorklet
scopes, but theWindow
branch will fail outside of a fenced frame tree with network disabled.This patch also specifies a new Permissions Policy,
fenced-unpartitioned-storage-read
, which can be used to disable access toget()
in fenced frames. Its default allowlist is*
.