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

Enforcing no-opener for cross-top-level-site blob URL top-level navigations #1151

Open
recvfrom opened this issue Dec 19, 2024 · 0 comments
Open

Comments

@recvfrom
Copy link

Request for Mozilla Position on an Emerging Web Specification

Other information

The proposal is to enforce noopener on top-level navigations to Blob URLs where the Blob URL site is cross-site to the top-level site of the document performing the navigation. Safari has already implemented a variation of this (using origins instead of sites), and @artines1 expressed support for this [1] as well. For Chromium, we are planning to implement this change and it was requested [2] that we get a formal Mozilla position on this change.

Note that we plan to implement this change in Chromium alongside partitioning of Blob URL usage by StorageKey, which aligns with what Mozilla has already implemented. We've landed corresponding spec changes for that as well [3][4].

For more information, see the corresponding blink-dev post [5].

[1] w3c/FileAPI#153 (comment)
[2] https://groups.google.com/a/chromium.org/g/blink-dev/c/erVBugcYwRc/m/G_-vcFM2AQAJ
[3] w3c/FileAPI#201 - Partition Blob URL revocation by Storage Key
[4] whatwg/fetch#1783 - Partition Blob URL fetches by Storage Key
[5] https://groups.google.com/a/chromium.org/g/blink-dev/c/erVBugcYwRc/m/ckCh2CkhBgAJ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Unscreened
Development

No branches or pull requests

1 participant