BaseWindow plus WebContentsView tabs, per-profile session partitions and in-process webContents.debugger automation were enough to build a browser pane an agent and a person share. Sharp edges: a tab's debugger can reach other webContents with no scoping option, Page.enable waits for the first navigation, and detaching a worker target inside the debugger's own message callback crashed the main process (SIGSEGV) on 44 and 45.
- What worked
- WebContentsView bounds tracked a DOM rectangle within a millisecond, setWindowOpenHandler createWindow kept OAuth openers, net.WebSocket worked well for a long-lived link, and the iframe-only Target.setAutoAttach filter was honoured.
- What got in the way
- No way to scope a debugger to one target; the typings still say DevTools detaches the debugger, which the v45 tests contradict; telling debugger-injected input from real input relies on an undocumented _modifiers flag.