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

COOP: choosing a browsing context doesn't consider "same-origin + COEP" #5165

Closed
zcorpan opened this issue Dec 17, 2019 · 1 comment
Closed

COOP: choosing a browsing context doesn't consider "same-origin + COEP" #5165

zcorpan opened this issue Dec 17, 2019 · 1 comment
Labels
topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal.

Comments

@zcorpan
Copy link
Member

zcorpan commented Dec 17, 2019

https://gist.github.com/annevk/6f2dd8c79c77123f39797f6bdac43f3e#changes-to-choosing-a-browsing-context

If current's top-level browsing context's active document's cross-origin opener-policy is "same-origin", then:

Should this be

If current's top-level browsing context's active document's cross-origin opener-policy is "same-origin" or "same-origin + COEP", then:

?

@annevk @jugglinmike
@zcorpan zcorpan added the topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal. label Dec 17, 2019
@annevk
Copy link
Member

annevk commented Dec 20, 2019

Yeah, that seems correct. If this happens a lot I guess we'll have to consider some grouping terminology.

@annevk annevk closed this as completed Dec 20, 2019
noamr added a commit to noamr/html that referenced this issue Sep 8, 2020
@noamr
Apply same-origin clarifications after whatwg#5165
b85af6b
noamr added a commit to noamr/html that referenced this issue Sep 8, 2020
@noamr
Apply same-origin clarifications after whatwg#5165
5b8ebc7
zcorpan pushed a commit to noamr/html that referenced this issue May 28, 2021
@noamr @zcorpan
Apply same-origin clarifications after whatwg#5165
b0c8616
noamr added a commit to noamr/html that referenced this issue Jun 27, 2021
@noamr
Apply same-origin clarifications after whatwg#5165
7f09870
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal.
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zcorpan @annevk