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
Implement a node.js-free, sandboxed, context isolated renderer #92164
Comments
|
An "implict" node-dependency that's not listed here is code loading. Today, the loader uses the |
|
Bootstrap sandboxed workbench code pointers:
|
|
@bpasero we shouldn't mix localization support in the Web with support for Node free renderer. We need a very different story for the Web whereas for a node free renderer we can still install the LP on the local disk. We can simply not access them from the renderer. So I will change the item (I have discussed it that way with @egamma as well) |
|
368f44e enables iframe based webviews on desktop when search functionality is not required. We'll get testing of the iframe based webviews during 1.56 insiders |
|
FYI following up on #116337, I believe the slowness I sometimes see with terminals is a result of the multiple process jumps since we can't communicate directly between the renderer and pty host yet. Was there an issue tracking this direct channel between renderer to arbitrary node process? |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
|


We want to explore a model where the workbench in Electron does not access node.js APIs. In that model the Electron renderer process runs in sandboxed mode, much like any browser tab would do. Privileged code has to either move into a backend process and be accessible via IPC communication or into a preload script that exposes certain methods to the page.
February
On Deck
electron-browsertoelectron-sandboxBacklog
sandbox: truebehind a dev settingipcRenderervia preload vs. directMessagePortto main processUint8ArrayoverBufferfor large data transfers (e.g. file IO)common/browser: run inBrowserWindowwithsandbox: truenode.js/electron-browser: run inELECTRON_RUN_AS_NODEArchitecture
The text was updated successfully, but these errors were encountered: