NW.js and Native OS Dialogs: Balancing Background State with UI Blocking

Answer

Yes. A synchronous native dialog (e.g., nw.Window.get().showMessageBox or nw.Gui.showMessageBox) invoked from the node‑main script runs on the process’s main thread, which is also the Chromium UI thread. While the dialog is modal, the UI thread is blocked, so all open Chromium windows stop rendering and become unresponsive until the dialog is dismissed.

Confirmed facts

• The node‑main script shares the same main thread as the renderer; there is no separate UI thread for background work.
• Native message‑box dialogs are synchronous in all current NW.js releases.
• Blocking occurs regardless of whether the call originates from the DOM or from node‑main.

Recommended pattern

1. Perform any background initialization in node‑main.
2. When a system alert is needed, send a message to the renderer process instead of showing the dialog directly. Example using postMessage:

// node‑main.js
const gui = require('nw.gui');
const win = gui.Window.get();
// after background work:
win.window.postMessage({ showAlert: true, message: 'Ready' }, '*');

// In each browser window (or a shared preload script)
window.addEventListener('message', function(e) {
  if (e.data && e.data.showAlert) {
    const gui = require('nw.gui');
    gui.Window.get().showMessageBox(e.data.message);
  }
});

1. If you must keep the call in node‑main, yield the event loop first:

setTimeout(() => {
  gui.Window.get().showMessageBox('Background alert');
}, 0);

This lets any pending UI tasks run before the modal appears, though the dialog will still block the UI once shown.

1. Alternative: create a hidden auxiliary window whose sole purpose is to host native dialogs; node‑main instructs that window to show the dialog, keeping the main application windows responsive.

When to ask for more detail

If you observe that the UI does not freeze despite using a synchronous dialog from node‑main, let me know the exact NW.js version you are running, as behavior can differ between pre‑0.14 and post‑0.14 releases.