Closed tamnguyenswe closed 1 month ago
Facing same issue
coming from xterm here I think
I have the same problem on Fedora 40 Sway.
After I click Try Again
, it will create a non-interoperable terminal.
I'm also having this issue, I thought it might be a problem with WSL but it started for me after updating to VSCode 1.92.0
QUICK FIX!!!
Just create a new In-window terminal and drag it to the new terminal window. 👍
Will this be hotfixed or should we downgrade?
@michaelschufi sorry this won't get a patch release as there's a few workarounds. To downgrade in the meantime you can grab 1.91.1 here https://code.visualstudio.com/updates/v1_91, you'll also want to set "update.mode": "none"
Hi.
QUICK FIX!!! Just create a new In-window terminal and drag it to the new terminal window. 👍
Didn't do the trick for me. Other hack: Ctrl+J (new term in main window) > Ctrl + Shift + P > Terminal: Move Into New Window > Drag & Drop into wanted window. Cumbersom many many times a day.
Does this issue occur when all extensions are disabled?: Yes
Error message:
The editor could not be opened due to an unexpected error: Not allowed to create elements in child window JavaScript context. Always use the main window so that "xyz instanceof HTMLElement" continues to work.
Steps to Reproduce:
Creating terminal in main window and drag it to side windows does work, but I have to do that with every window reload. Yesterday I could still use terminals in side windows like normal, this only occured after updating to 1.92 July update Thanks for reading :)