<p dir="auto">We have made several changes to the window.open functionality to use the native blink/chromium code, but we are always working with embedded views so I'm looking for a little help to upstream this without breaking other use cases<br>
Starting from <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/brave/muon/commit/6ee28c3927a34495fb0a059ac3071e6e14358743/hovercard" href="https://github.com/brave/muon/commit/6ee28c3927a34495fb0a059ac3071e6e14358743">brave/muon@<tt>6ee28c3</tt></a> to <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/brave/muon/commit/9dc98b1448f1efa1f2898fb714643df2b3474b12/hovercard" href="https://github.com/brave/muon/commit/9dc98b1448f1efa1f2898fb714643df2b3474b12">brave/muon@<tt>9dc98b1</tt></a><br>
We are working on getting the remaining electron tests passing and I'm happy to create a pull request as the basis for this, but some help/feedback would be welcome. Thanks!</p>
<p dir="auto">when opening a new window using window.open, we currently get a BrowserWindowProxy that only support posting messages.</p>
<p dir="auto">Some websites, webapps and libraries uses <code class="notranslate">window.opener</code> to access properties and objects of the opener window. Thoose are broken in Electron.<br>
That's the case for example of Chromium devtools, that use window.open / window.opener in dockable/undockable mode.</p>