ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #electron
Goal Confirm whether an API exposed through contextBridge.exposeInMainWorld remains available on window after a same-process renderer navigation that does not reload the page, with contextIsolation enabled. Constraints Electron runs preload scripts in an isolated world, and same-process navigations may not re-execute the preload script. Behavior can differ b
Resource Management in Electron Wrapper The Notion desktop application utilizes an Electron wrapper to render the web-based interface. While the standalone web client maintains stable memory profiles within a browser sandbox, the desktop client exhibits progressive RAM consumption during extended sessions, particularly when rendering embedded external conten
Electron version 12 and later default to contextIsolation: true to prevent renderer processes from accessing Node.js internals. This security boundary is designed to stop unauthorized public access to system APIs by separating the JavaScript contexts of the preload script and the renderer. While contextBridge allows the definition of a controlled gateway for
Repeated auth challenges in Electron I'm handling HTTP authentication in an Electron app via app.on('login') . My handler calls event.preventDefault() and supplies cached credentials with callback(username, password) . When those credentials expire or are rejected by the server, the login event fires again for the same origin, and my handler keeps supplying
Goal Ensure that the commit message field in GitKraken’s commit dialog is perceivable and operable for users who rely on screen readers and keyboard navigation, without altering existing Git workflow shortcuts. Constraints and Uncertainty The field is implemented as a custom Electron widget that currently lacks explicit ARIA roles, so its role is only inferr
The goal is to characterize the runtime behavior of Electron's ipcRenderer.invoke when the corresponding ipcMain.handle never transmits a reply. This scenario arises in long-running or faulted main-process handlers where no explicit resolution occurs. Understanding whether the promise remains pending, rejects after an implicit timeout, or causes renderer res
An Electron application needs to move a large analytical dataset from the Main process to a Renderer process for visualization. The current design sends the complete array through ipcMain and ipcRenderer , relying on JSON serialization across the Mojo-based IPC bridge. The goal is to identify the precise point where this pattern stops scaling and requires a
Electron's security model relies on the separation of the Main and Renderer processes. While contextIsolation is enabled by default in modern versions to prevent prototype pollution, there are scenarios where specific Node.js capabilities are required within the renderer's logic without exposing the entire Node.js API to the web content. The primary constrai
Electron's security model relies on contextIsolation to separate the renderer process from the main process. To facilitate communication, the contextBridge module allows developers to expose a limited API from a preload script to the renderer's global window object. A critical design concern arises when complex objects or entire Electron modules are passed t