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.

Sign up for GitHub

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

Use window.anonymous instead of document.anonymous #26

Merged
merged 1 commit into from
Dec 10, 2021
Merged

Use window.anonymous instead of document.anonymous #26

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: 2 additions & 2 deletions anonymous_iframes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ In parallel with the iframe attribute, we plan to add a new Fetch Metadata heade
* `Sec-Fetch-COEP: credentialless`: the resource will be rendered in a context with a COEP of credentialless.
* `Sec-Fetch-COEP: anonymous`: the resource will be rendered in an anonymous iframe.

Additionally, we plan on adding a `document.anonymous` read-only attribute. By
Additionally, we plan on adding a `window.anonymous` read-only attribute. By
default, this will return `false`. In anonymous iframes it will return `true`,
allowing a document to check whether it was loaded in an anonymous iframe.

Expand Down Expand Up @@ -198,7 +198,7 @@ This solution runs into compatibility issues:

#### What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?

The `Sec-Fetch-COEP` header exposes the COEP of the environment a resource will be rendered in. This allows a server to decline answering a request if they do not want their resource to be embedded in a more dangerous environment. The `Document.credentials` method exposes whether a document is loaded in an anonymous iframe or not, allowing a document to change its behavior depending on the availability of existing credentials or stored resources.
The `Sec-Fetch-COEP` header exposes the COEP of the environment a resource will be rendered in. This allows a server to decline answering a request if they do not want their resource to be embedded in a more dangerous environment. The `window.anonymous` method exposes whether a document is loaded in an anonymous iframe or not, allowing a document to change its behavior depending on the availability of existing credentials or stored resources.

#### Do features in your specification expose the minimum amount of information necessary to enable their intended uses?

Expand Down