docs: precise that node integration is enabled in natively opened window if nodeIntegrationInSubFrames is true (#19142)

This commit is contained in:
Alexandre Lacheze
2019-07-10 17:37:28 +02:00
committed by Shelley Vohr
parent 733251866c
commit 51f03033a4
2 changed files with 3 additions and 3 deletions

View File

@@ -118,7 +118,7 @@ const w = new BrowserWindow({
### `nativeWindowOpen`
Child windows opened with the `nativeWindowOpen` option will always have Node.js integration disabled.
Child windows opened with the `nativeWindowOpen` option will always have Node.js integration disabled, unless `nodeIntegrationInSubFrames` is `true.
## Privileged Schemes Registration

View File

@@ -256,7 +256,7 @@ It creates a new `BrowserWindow` with native properties as set by the `options`.
enabled in web workers. Default is `false`. More about this can be found
in [Multithreading](../tutorial/multithreading.md).
* `nodeIntegrationInSubFrames` Boolean (optional) - Experimental option for
enabling NodeJS support in sub-frames such as iframes. All your preloads will load for
enabling Node.js support in sub-frames such as iframes and child windows. All your preloads will load for
every iframe, you can use `process.isMainFrame` to determine if you are
in the main frame or not.
* `preload` String (optional) - Specifies a script that will be loaded before other
@@ -353,7 +353,7 @@ It creates a new `BrowserWindow` with native properties as set by the `options`.
Console tab.
* `nativeWindowOpen` Boolean (optional) - Whether to use native
`window.open()`. Defaults to `false`. Child windows will always have node
integration disabled. **Note:** This option is currently
integration disabled unless `nodeIntegrationInSubFrames` is true. **Note:** This option is currently
experimental.
* `webviewTag` Boolean (optional) - Whether to enable the [`<webview>` tag](webview-tag.md).
Defaults to `false`. **Note:** The