Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
When detaching an active browser preview tab to a new standalone window (via right-click context menu), the preview window becomes completely non-interactive. DOM event listeners and user interactions (mouse clicks, scroll events, keyboard input) appear to be disconnected or severed from the browser runtime.
Symptom manifestation:
- The page renders visually but all interactivity is frozen
- Neither click events nor scroll wheel input registers
- Developer tools interactions (element inspector, console evaluation) do not function
- The same tab works perfectly when remaining in the IDE’s native browser view
This suggests a potential issue with event binding transfer or IPC/bridge communication when spawning a detached window process in Electron.
Steps to Reproduce
- Launch Cursor IDE v2.4.22
- Navigate to the built-in browser preview (e.g., open any web dev project with a running dev server on localhost)
- Within the browser tab, right-click the tab header
- Select “Move into new window”
- Attempt basic interactions: scroll page, click buttons, type in text fields
- Open DevTools in the detached window and try to execute commands
Expected: Full browser functionality identical to the integrated preview
Observed: Complete input freeze - no mouse or keyboard events process
Frequency: 100% reproducible, occurs on both notebook and desktop systems
Environment affected: Windows 10/11, both clean installations and upgraded systems show identical behavior post-update from 2.4.21 to 2.4.22
Expected Behavior
The detached window should maintain full feature parity with the integrated browser preview, including responsive event handling for all user interactions (mouse, keyboard, scroll). Developer console should function normally. All Chromium/browser APIs should remain accessible and functional. IPC communication between main process and renderer should not be disrupted by window detachment.
Operating System
Windows 10/11
Version Information
Version: 2.4.22
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Build Type: Stable
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
Additional Information
Investigation shows this appears to be a regression introduced between v2.4.21 and v2.4.22. Possible causes to investigate: Electron window spawning changes, IPC bridge initialization during window detachment, or changes to Chromium’s event loop handling in detached webview contexts.
Workaround: Keep preview tab within IDE window only, limiting multi-monitor and workflow efficiency.
Affects: Web developers using Cursor for local development and live preview features.
Does this stop you from using Cursor
Yes - Cursor is unusable