Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Webview views in Cursor do not render correctly when placed in the bottom panel (where Terminal / Problems normally live).
When a webview is hosted in that location, Cursor outputs service worker registration errors and the view remains blank, even though the extension itself is functioning and the webview loads fine in other locations.
This affects the Snowflake VS Code extension’s query results view, but the underlying issue appears to be with Cursor’s handling of webviews in the bottom panel, not with the extension itself.
When the exact same view is moved to the Primary Side Bar, the webview renders normally and behaves as expected.
Steps to Reproduce
1. Install any VS Code extension that contributes a webview view (e.g., Snowflake’s VS Code extension).
2. Place its webview (e.g., “Query Results” view) in the bottom panel:
• Right-click view tab → “Move View → Panel”
3. Trigger the extension to open or refresh its webview.
4. Observe:
• The bottom panel switches to the correct tab,
• But the view is blank,
• And the devtools console shows service worker errors such as: "Found unexpected service worker controller... Waiting for controllerchange."
5. Now move the same webview to the Primary Side Bar:
• Right-click the tab → “Move View → Primary Side Bar”
6. Re-trigger the extension.
7. The webview now renders correctly with no errors.
Expected Behavior
Webview-based extension views should behave consistently regardless of whether they are placed in:
• the Primary Side Bar
• the Secondary Side Bar
• the Bottom Panel
Cursor should successfully initialize the webview and its service worker in all supported view containers.
Currently, webviews work in the side bar but fail to initialize in the bottom panel, which breaks extensions that expect to show results/output there.
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.50 (Universal)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0
Does this stop you from using Cursor
No - Cursor works, but with this issue
