-
Notifications
You must be signed in to change notification settings - Fork 16k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: Add ElectronBrowserContext::BrowserContexts()
#46089
Conversation
2d1f658
to
1e44ee8
Compare
ElectronBrowserContext::BrowserContexts()
…owserMainParts::PostMainMessageLoopRun()
…tensionsBrowserClient::IsValidContext()
…tensionsBrowserClient::BroadcastEventToRenderers()
decouple ElectronExtensionsBrowserClient from the internals of ElectronBrowserContext
1e44ee8
to
b1fc0ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
No Release Notes |
I was unable to backport this PR to "35-x-y" cleanly; |
I have automatically backported this PR to "36-x-y", please check out #46158 |
I have automatically backported this PR to "34-x-y", please check out #46159 |
Description of Change
This is to tighten down controls on how
ElectronBrowserContext
is accessed and to reduce leaking implementation details. Callers should not have mutable access to the context map. Callers shouldn't even need to know the context map exists 🙂Checklist
npm test
passesRelease Notes
Notes: none.