Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add spec for APIs gated on network revocation. #204

Merged
merged 4 commits into from
Jan 14, 2025

Conversation

VergeA
Copy link
Collaborator

@VergeA VergeA commented Jan 10, 2025

After untrusted network access has been disabled in a fenced frame via disableUntrustedNetwork(), script running in the frame will gain access to new powerful APIs. This patch provides an algorithm that other specs can use when implementing methods that should only succeed in a fenced frame with network access revoked.

Currently, the only method that will rely on this algorithm is SharedStorage.get(), which is implemented in the Shared Storage draft spec. I'm planning to update that spec separately after this PR merges.


Preview | Diff

After untrusted network access has been disabled in a fenced frame
via disableUntrustedNetwork(), script running in the frame will gain
access to new powerful APIs. This patch provides an algorithm that other
specs can use when implementing methods that should only succeed in a
fenced frame with network access revoked.

Currently, the only method that will rely on this algorithm is
SharedStorage.get(), which is implemented in the Shared Storage draft
spec. I'm planning to update that spec separately after this PR merges.
@VergeA VergeA requested a review from blu25 January 10, 2025 17:27
Copy link
Collaborator

@blu25 blu25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Algorithm looks good. Just one question on the introductory paragraph.

spec.bs Outdated Show resolved Hide resolved
@VergeA VergeA requested a review from domfarolino January 10, 2025 22:19
defined in the [[Shared-Storage]] draft specification.

<div algorithm>
To <dfn export>determine if a navigable has fully revoked network</dfn> given a [=navigable=]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, since we're exporting this, is there a corresponding PR made in the Shared Storage spec yet?

Copy link
Collaborator Author

@VergeA VergeA Jan 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, not yet. I started working on one a while ago, but there's been some refactors to the spec since then. I was waiting to rewrite it until this PR landed, so I could have a correctly-exported definition and my Shared Storage spec would build properly.

spec.bs Outdated Show resolved Hide resolved
spec.bs Show resolved Hide resolved
@domfarolino domfarolino merged commit 82a9f09 into WICG:master Jan 14, 2025
2 checks passed
@VergeA VergeA deleted the special branch January 14, 2025 19:38
github-actions bot added a commit that referenced this pull request Jan 14, 2025
SHA: 82a9f09
Reason: push, by domfarolino

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants