mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

add some markdown links

Browse source
This commit is contained in:
Toinane 2017-11-29 12:13:45 +01:00
parent 0a0d88a5dc
commit 3d4ef66775
No known key found for this signature in database
GPG key ID: 1A3729C1B6D59115
6 changed files with 10 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/api/sandbox-option.md
View file

@ -33,7 +33,7 @@ which has access to a subset of the electron renderer API.
Another difference is that sandboxed renderers don't modify any of the default
JavaScript APIs. Consequently, some APIs such as `window.open` will work as they
do in chromium (i.e. they do not return a `BrowserWindowProxy`).
do in chromium (i.e. they do not return a [`BrowserWindowProxy`](browser-window-proxy.md)).
## Example
@ -51,9 +51,9 @@ app.on('ready', () => {
})
```
In the above code the `BrowserWindow` that was created has node.js disabled and can communicate
In the above code the [`BrowserWindow`](browser-window.md) that was created has node.js disabled and can communicate
only via IPC. The use of this option stops electron from creating a node.js runtime in the renderer. Also,
within this new window `window.open` follows the native behaviour (by default electron creates a `BrowserWindow`
within this new window `window.open` follows the native behaviour (by default electron creates a [`BrowserWindow`](browser-window.md)
and returns a proxy to this via `window.open`).
It is important to note that this option alone won't enable the OS-enforced sandbox. To enable this feature, the