Define interaction with Cross-Origin-Opener-Policy ?

[mzealey]

In latest Chrome at least, if I present a url of /presentation.html (ie within the same origin as the main page) but serve Cross-Origin-Opener-Policy: same-origin on that, chrome returns a blocked content page and closes the presentation. I don't fully understand how COOP/COEP should interact with presentation API to know if this is a proper bug as such, however it is perhaps something that could be specified explicitly in this document?

[markafoltz]

The Presentation API requires that documents opened as presentations are in a distinct browsing context from the controller (opener), so this behavior is expected. I agree that the spec should be explicit about this.