Managing Application Shells in NW.js: Browser Window vs. NW.Window API
Learn how to choose between the standard Window object and the NW.js Window API to manage native OS behaviors like frameless windows and always-on-top states.
Loading…
ReadMeFeed / Community knowledge
#nw-js
Real questions. Useful conversations. Find the people who know your stack.
nodewebkitNW.js package.json nodejs integration and remote URL boundaries
Node.js Integration in Mixed Contexts NW.js allows the execution of Node.js APIs directly within the DOM context by setting "nodejs": true in the package.json configuration. This integration enables seamless access to the filesystem and OS-level operations from the client-side JavaScript environment. Security Boundary Constraints A critical design concern ar
NW.js packaged app accessibility tree exposure and screen reader configuration
A packaged NW.js application relies on the bundled Chromium accessibility tree to expose DOM roles, labels and states to native assistive technologies. The user-facing workflow needs predictable screen reader compatibility across platforms, but there is no documented NW.js configuration that explicitly controls or tests that mapping. Accessibility support is
Failed global shortcut registration in nw.App.registerGlobalHotKey
Failed global shortcut registration in nw.App.registerGlobalHotKey When an NW.js application calls nw.App.registerGlobalHotKey , the API returns a boolean. A return value of false indicates that the registration did not succeed, but the documentation does not expose the underlying reason—whether the shortcut is already in use by another process, the accelera