Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

window.open does not give correct window/opener access based on browsing contenxt #137

Closed
bridiver opened this issue Jan 11, 2016 · 2 comments

Comments

@bridiver
Copy link
Collaborator

The webcontents are created correctly, but electron runs each webview in its own process which breaks the connection. I believe the fix is to add support for guest view into libchromium content and electron to handle the swappedout:// condition. There could also potentially be changes to how/when electron creates new render processes to match the process-per-site-instance model https://www.chromium.org/developers/design-documents/process-models

@bridiver
Copy link
Collaborator Author

partially fixed by brave/muon#2
still need to go back and remove the browserproxy stuff

@bridiver bridiver reopened this Jan 15, 2016
@bridiver
Copy link
Collaborator Author

brave/muon#3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant