#964: `noopener-allow-popups` value in COOP
Discussions
2024-06-24
Matthew: Off-topic, but: the explainer for that talks about where you have multiple, separate applications in the same domain... that's the same topic we're working with in API - known destinations...
2024-07-29
Dan: could this be another decline?
Martin: I think it could be ... last I looked, it has a good explainer.. it looks like this sparking conversation in the webappsec working group, That's a good thing. Really what you need to do is take this to the right working group.
Martin: writes some text
Thanks for highlighting this problem Yoav. A small breakout group looked at this today and it seems like you have started an interesting discussion with a few people about the topic. We encourage you to continue that discussion. The Web Application Security Working Group seems like a pretty natural place to take this work. For now, we'd suggest that our input to that discussion would not be as useful as that of the people you are already discussing this with, so we're going to decline this review.
OpenedJun 5, 2024
こんにちは TAG-さん!
I'm requesting a TAG review for adding a
noopener-allow-popups
value to COOP.The noopener-allow-popups Cross-Origin-Opener-Policy value severs the opener relationship between the document loaded with this policy and its opener. At the same time, the opened document can open further documents (as the "allow-popups" in the name suggests) and maintain its opener relationship with them, assuming that their COOP policy allows it.
Further details:
You should also know that...
[please tell us anything you think is relevant to this review]