| 00:15 | <Domenic> | Hmm, Matrix seemed to duplicate my message here but then it didn't. Anyway:
We have an extension that opens two windows side-by-side and records the screen for user research. One of these windows opens an arbitrary document. With Manifest V3 coming and improvements to web standards we are looking to move away from the extension in favour of just a website.
We've had good initial success with window.open to open and position the two windows side by side. However, we've recently realised that COOP(when the origin sets same-origin) puts a spanner in the works. We really only need the ability to open popups, position them, close them, and change their URL. It seems that with COOP we are dead in the water on the closing and changing URL components of this however.
So I guess my question is: With a more widespread deployment of COOP is there no way to achieve our goals here(outside of keeping an extension?).
In general, if a website does not want you to control their content, you cannot. In particular if they use COOP to deny you from having such control. One day we might even make COOP the default, like it should have been from the beginning, so that websites have to give up such control affirmatively. |
| 00:15 | <Domenic> | annevk: Should I rewrap adjacent lines to the ones I'm touching (like if they end up significantly under 100 chars, etc) or should I prefer to leave untouched lines alone to reduce conflicts? I generally rewrap per "paragraph", i.e. \n\n-delimited chunk |
| 00:16 | <Domenic> | https://github.com/whatwg/html/actions/runs/3396297480/jobs/5647202077 This is due to https://github.com/whatwg/whatwg.org/issues/401 . Not your fault, don't worry about it, and we'll hope to have it fixed soon. |