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

Jump to bottom

What should happen if the top-level origin is an opaque origin #40

Closed
annevk opened this issue May 21, 2020 · 0 comments · Fixed by #49
Closed

What should happen if the top-level origin is an opaque origin #40

annevk opened this issue May 21, 2020 · 0 comments · Fixed by #49
Assignees
@hober
Labels
needs edit This issue is waiting on a PR to be written.

Comments

@annevk
Copy link
Collaborator

annevk commented May 21, 2020

A top-level document can sandbox itself. If it embeds tracker.example and that were to invoke requestStorageAccess(), what should happen?

I suspect we should disallow in this case as you cannot have meaningful UI.

We also generally do not allow storage for opaque origins so maybe storage would be disabled for the entire frame tree?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hober hober

Labels
needs edit This issue is waiting on a PR to be written.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Disallow storage access when the top-level origin is an opaque origin. privacycg/storage-access
2 participants
@hober @annevk