smaug----
smaug----
I'd expect consistency with showModal() which has the connected check.
So how should this work if a new window is first opened with page A and then later navigated to B and only B uses the new header? The Window(Proxy)...
ok, and how does "noopener" in the new value hint about that behavior? Isn't the change you want a tweak to https://html.spec.whatwg.org/#matching-coop so that in some cases that same origin...
That, and also this feels like a distinct feature of COOP itself, just like the existing noopener is a feature of its own.
But noopener itself is already a separate functionality in the platform. Is there a reason to not let opened page pages control opener relationship without binding that functionality to COOP....
We discussed about this, and I can live with this. But this needs some documentation outside the normal COOP parts so that people trying to optimize for example bfcache handling...
It does. But having something called Cross-Origin-Opener-Policy being possibly in a critical path on enabling bfcache even on same origin pages is a bit confusing.
Right, but you have the existing noopener for those cases.
I think I might want to see the explainer go through the known [issues](https://github.com/WICG/canvas-place-element/blob/main/QUESTIONS.md) in some more detail before moving this to [stage 1](https://whatwg.org/stages#stage1). Especially hit testing can be rather...
I was referring to "A comprehensive explainer " as requirement for stage 1. A bit nitpicking, I know, but there were quite a few unknowns still.