-
Notifications
You must be signed in to change notification settings - Fork 38.8k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugconfirmedIssue has been confirmed by VS Code Team memberIssue has been confirmed by VS Code Team memberinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersterminal-editorsupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)upstream-issue-fixedThe underlying upstream issue has been fixedThe underlying upstream issue has been fixedupstream-issue-linkedThis is an upstream issue that has been reported upstreamThis is an upstream issue that has been reported upstreamverifiedVerification succeededVerification succeeded
Milestone
Description
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.92.0, commit b1c0a14
- OS Version: Windows 10 Enterprise, 22H2 build 19045.4651
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:
- Open a new VS code window

- Create a new file and drag out to make another window

- Run "Create New Terminal in Editor Area" on that new window

- The error will show up

- Clicking "Try Again" will reload the terminal, but it doesn't accept inputs, cannot type anything there

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 :)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugconfirmedIssue has been confirmed by VS Code Team memberIssue has been confirmed by VS Code Team memberinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersterminal-editorsupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)upstream-issue-fixedThe underlying upstream issue has been fixedThe underlying upstream issue has been fixedupstream-issue-linkedThis is an upstream issue that has been reported upstreamThis is an upstream issue that has been reported upstreamverifiedVerification succeededVerification succeeded