-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Cross-Origin-Opener-Policy: provide a clearer spec. #4580
Labels
clarification
Standard could be clearer
topic: cross-origin-opener-policy
Issues and ideas around the new "inverse of rel=noopener" header.
Comments
I agree that it'd be good to add this. I'm personally focusing on
so it'd be great if someone were willing to pick this up. |
annevk
added
the
topic: cross-origin-opener-policy
Issues and ideas around the new "inverse of rel=noopener" header.
label
May 13, 2019
@hemeryar, @ParisMeuleman or myself will pick this up once we're done with Chrome's implementation of COOP. |
camillelamy
added a commit
to camillelamy/html
that referenced
this issue
Mar 4, 2020
I have a draft PR at #5334 that takes https://gist.github.com/annevk/6f2dd8c79c77123f39797f6bdac43f3e and merges it into the spec. |
camillelamy
added a commit
to camillelamy/html
that referenced
this issue
Mar 12, 2020
camillelamy
added a commit
to camillelamy/html
that referenced
this issue
Mar 12, 2020
Tests: https://github.com/web-platform-tests/wpt/tree/master/html/cross-origin-opener-policy Closes: whatwg#4580 Fix formatting issues Fix some more formatting issues Addressed code review comments Addressed comments Addressed comments
camillelamy
added a commit
to camillelamy/html
that referenced
this issue
Apr 22, 2020
Tests: https://github.com/web-platform-tests/wpt/tree/master/html/cross-origin-opener-policy Closes: whatwg#4580 Fix formatting issues Fix some more formatting issues Addressed code review comments Addressed comments Addressed comments
camillelamy
added a commit
to camillelamy/html
that referenced
this issue
Apr 22, 2020
Tests: https://github.com/web-platform-tests/wpt/tree/master/html/cross-origin-opener-policy Closes: whatwg#4580 Fix formatting issues Fix some more formatting issues Addressed code review comments Addressed comments Addressed comments
camillelamy
added a commit
to camillelamy/html
that referenced
this issue
May 4, 2020
Tests: https://github.com/web-platform-tests/wpt/tree/master/html/cross-origin-opener-policy Closes: whatwg#4580 Fix formatting issues Fix some more formatting issues Addressed code review comments Addressed comments Addressed comments change some formatting and the non-normative explanations oops nit
camillelamy
added a commit
to camillelamy/html
that referenced
this issue
May 4, 2020
Tests: https://github.com/web-platform-tests/wpt/tree/master/html/cross-origin-opener-policy Closes: whatwg#4580 Fix formatting issues Fix some more formatting issues Addressed code review comments Addressed comments Addressed comments change some formatting and the non-normative explanations oops nit
annevk
added a commit
to camillelamy/html
that referenced
this issue
Jun 5, 2020
Fixes whatwg#3740. Closes whatwg#4580. Need to check again if it closes them: * whatwg#4921 * whatwg#5168 * whatwg#5172 * whatwg#5198 (probably not?) Co-authored-by: Anne van Kesteren <[email protected]>
camillelamy
pushed a commit
to camillelamy/html
that referenced
this issue
Jun 10, 2020
Fixes whatwg#3740. Closes whatwg#4580. Need to check again if it closes them: * whatwg#4921 * whatwg#5168 * whatwg#5172 * whatwg#5198 (probably not?) Co-authored-by: Anne van Kesteren <[email protected]>
camillelamy
pushed a commit
to camillelamy/html
that referenced
this issue
Jun 16, 2020
Fixes whatwg#3740. Closes whatwg#4580. Need to check again if it closes them: * whatwg#4921 * whatwg#5168 * whatwg#5172 * whatwg#5198 (probably not?) Co-authored-by: Anne van Kesteren <[email protected]>
camillelamy
pushed a commit
to camillelamy/html
that referenced
this issue
Jun 24, 2020
Fixes whatwg#3740. Closes whatwg#4580. Need to check again if it closes them: * whatwg#4921 * whatwg#5168 * whatwg#5172 * whatwg#5198 (probably not?) Co-authored-by: Anne van Kesteren <[email protected]>
domenic
added a commit
that referenced
this issue
Jun 24, 2020
This commit adds the notion of cross-origin opener policy (COOP). COOP allows websites to restrict which origins they share their browsing context group with. annevk wrote a first draft of the behavior of COOP here: https://gist.github.com/annevk/6f2dd8c79c77123f39797f6bdac43f3e. This takes that draft and merges it into the spec, with many updates along the way. Closes #3740. Closes #4580. Closes #4921. Closes #5172. Co-authored-by: clamy <[email protected]> Co-authored-by: Anne van Kesteren <[email protected]> Co-authored-by: Domenic Denicola <[email protected]>
mfreed7
pushed a commit
to mfreed7/html
that referenced
this issue
Sep 11, 2020
This commit adds the notion of cross-origin opener policy (COOP). COOP allows websites to restrict which origins they share their browsing context group with. annevk wrote a first draft of the behavior of COOP here: https://gist.github.com/annevk/6f2dd8c79c77123f39797f6bdac43f3e. This takes that draft and merges it into the spec, with many updates along the way. Closes whatwg#3740. Closes whatwg#4580. Closes whatwg#4921. Closes whatwg#5172. Co-authored-by: clamy <[email protected]> Co-authored-by: Anne van Kesteren <[email protected]> Co-authored-by: Domenic Denicola <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
clarification
Standard could be clearer
topic: cross-origin-opener-policy
Issues and ideas around the new "inverse of rel=noopener" header.
Currently COOP is being implemented in Firefox and there are plans to add this to all other major browsers.
This feels like we got to the point where a clear specifications with intentions, thread model and mechanics should be put together.
I'm mostly interested in
Currently there is a tentative spec for the algorithm and a rather long dicussion that contains all the step that this proposal went through.
I read all that to try and understand what the policy should accomplish and I think I got it, but I also think this should be easier for newcomers, users and implementers to tackle and understand.
/cc @arturjanc @domenic @rniwa @annevk @csreis @mystor
The text was updated successfully, but these errors were encountered: