Skip to main content

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

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. This is the same behavior as in the browser.

When nativeWindowOpen is set to false, instead results in the creation of a BrowserWindowProxy, a light wrapper around BrowserWindow.

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.

Les options du constructeur BrowserWindow sont définies par ordre croissant de priorité : avec d'abord les options héritées du parent puis les options analysées à partir de la chaîne features de puis les webPreferences héritées du parent et liées à la sécurité et enfin les options données par webContents.setWindowOpenHandler. Note that webContents.setWindowOpenHandler has final say and full privilege because it is invoked in the main process.[, frameName][, features])

  • url String
  • frameName String (facultatif)
  • features String (facultatif)

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.

Par exemple :'', '_blank', 'top=500,left=200,frame=false,nodeIntegration=no')

Remarque :

  • L'intégration de Node sera toujours désactivée dans le nouveau window si elle est désactivée sur la fenêtre parent.
  • L'isolation du context sera toujours activée dans le nouveau window si elle est activée sur la fenêtre parent.
  • JavaScript sera toujours désactivé dans le nouveau window si il est désactivé sur la fenêtre parent.
  • Les fonctionnalités non standards (non gérées par Chromium ou Electron) renseignées dans features seront transmises à tout gestionnaire de l'événement did-create-window enregistré de webContents dans le paramètre options.
  • frameName suit la spécification de windowName située dans la documentation native.

To customize or cancel the creation of the window, you can optionally set an override handler with webContents.setWindowOpenHandler() from the main process. Returning { action: 'deny' } cancels the window. Returning { action: 'allow', overrideBrowserWindowOptions: { ... } } will allow opening the window and setting the BrowserWindowConstructorOptions to be 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.

Native Window example

// main.js
const mainWindow = new BrowserWindow()

// 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 {
action: 'allow',
overrideBrowserWindowOptions: {
frame: false,
fullscreenable: false,
backgroundColor: 'black',
webPreferences: {
preload: 'my-child-window-preload-script.js'
return { action: 'deny' }
// renderer process (mainWindow)
const childWindow ='', 'modal')

BrowserWindowProxy example

// main.js
const mainWindow = new BrowserWindow({
webPreferences: { nativeWindowOpen: false }

mainWindow.webContents.setWindowOpenHandler(({ url }) => {
if (url.startsWith('')) {
return { action: 'allow' }
return { action: 'deny' }

mainWindow.webContents.on('did-create-window', (childWindow) => {
// For example...
childWindow.webContents.on('will-navigate', (e) => {
// renderer.js
const windowProxy ='', null, 'minimizable=false')
windowProxy.postMessage('hi', '*')