Electron Releases

Description of Change

Fixes #53521.

A window.open() child of an opener with contextIsolation: false gets contextIsolation: true unless the handler overrides it. Its synchronous about:blank document still starts with the opener's WebPreferences, so its Node.js environment is created in the main world. Once the browser sends the child's own preferences, the observer and GetContext() pick the isolated world instead.

• The first IPC message to such a child created a context in the isolated world and hit CHECK(!environments_.contains(render_frame)). Before #52964 this created a second environment and ran the preload again.
• Navigating such a child skipped the release of its environment for the same reason. That crashed before #52964 as well.
• ElectronRendererClient now records the world of each frame's environment when it creates it. While the environment exists, only that world is notified of context creation and release (ShouldNotifyClient), and GetContext() returns the environment's context, so IPC reaches the preload that ran in it.
• The sandboxed renderer client keeps its current behavior.

Checklist

• PR description included
• npm test passes
• tests are added

Release Notes

Notes: Fixed a renderer crash when the main process sent IPC to, or a page navigated, a same-process window.open() child whose contextIsolation differed from its opener's.