Co-authored-by: Jeremy Rose <jeremya@chromium.org>
4.8 KiB
Opening windows from the renderer
There are several ways to control how windows are created from trusted or untrusted content within a renderer. Windows can be created from the renderer in two ways:
- clicking on links or submitting forms adorned with
target=_blank
- JavaScript calling
window.open()
In non-sandboxed renderers, or when nativeWindowOpen
is false (the default), this results in the creation of a
BrowserWindowProxy
, a light wrapper around
BrowserWindow
.
However, when the sandbox
(or directly, nativeWindowOpen
) option is set, a
Window
instance is created, as you'd expect in the browser. For same-origin
content, the new window is created within the same process, enabling the parent
to access the child window directly. This can be very useful for app sub-windows that act
as preference panels, or similar, as the parent can render to the sub-window
directly, as if it were a div
in the parent.
Electron pairs this native Chrome Window
with a BrowserWindow under the hood.
You can take advantage of all the customization available when creating a
BrowserWindow in the main process by using webContents.setWindowOpenHandler()
for renderer-created windows.
BrowserWindow constructor options are set by, in increasing precedence
order: options inherited from the parent, parsed options
from the features
string from window.open()
, security-related webPreferences
inherited from the parent, and options given by
webContents.setWindowOpenHandler
.
Note that webContents.setWindowOpenHandler
has final say and full privilege
because it is invoked in the main process.
window.open(url[, frameName][, features])
url
StringframeName
String (optional)features
String (optional)
Returns BrowserWindowProxy
| Window
features
is a comma-separated key-value list, following the standard format of
the browser. Electron will parse BrowserWindowConstructorOptions
out of this
list where possible, for convenience. For full control and better ergonomics,
consider using webContents.setWindowOpenHandler
to customize the
BrowserWindow creation.
A subset of WebPreferences
can be set directly,
unnested, from the features string: zoomFactor
, nodeIntegration
, preload
,
javascript
, contextIsolation
, and webviewTag
.
For example:
window.open('https://github.com', '_blank', 'top=500,left=200,frame=false,nodeIntegration=no')
Notes:
- Node integration will always be disabled in the opened
window
if it is disabled on the parent window. - Context isolation will always be enabled in the opened
window
if it is enabled on the parent window. - JavaScript will always be disabled in the opened
window
if it is disabled on the parent window. - Non-standard features (that are not handled by Chromium or Electron) given in
features
will be passed to any registeredwebContents
'sdid-create-window
event handler in theadditionalFeatures
argument.
To customize or cancel the creation of the window, you can optionally set an
override handler with webContents.setWindowOpenHandler()
from the main
process. Returning false
cancels the window, while returning an object sets
the BrowserWindowConstructorOptions
used when creating the window. Note that
this is more powerful than passing options through the feature string, as the
renderer has more limited privileges in deciding security preferences than the
main process.
BrowserWindowProxy
example
// main.js
const mainWindow = new BrowserWindow()
mainWindow.webContents.setWindowOpenHandler(({ url }) => {
if (url.startsWith('https://github.com/')) {
return true
}
return false
})
mainWindow.webContents.on('did-create-window', (childWindow) => {
// For example...
childWindow.webContents('will-navigate', (e) => {
e.preventDefault()
})
})
// renderer.js
const windowProxy = window.open('https://github.com/', null, 'minimizable=false')
windowProxy.postMessage('hi', '*')
Native Window
example
// main.js
const mainWindow = new BrowserWindow({
webPreferences: {
nativeWindowOpen: true
}
})
// In this example, only windows with the `about:blank` url will be created.
// All other urls will be blocked.
mainWindow.webContents.setWindowOpenHandler(({ url }) => {
if (url === 'about:blank') {
return {
frame: false,
fullscreenable: false,
backgroundColor: 'black',
webPreferences: {
preload: 'my-child-window-preload-script.js'
}
}
}
return false
})
// renderer process (mainWindow)
const childWindow = window.open('', 'modal')
childWindow.document.write('<h1>Hello</h1>')