-
Notifications
You must be signed in to change notification settings - Fork 34.7k
Closed
Labels
custom-editorsCustom editor API (webview based editors)Custom editor API (webview based editors)feature-requestRequest for new features or functionalityRequest for new features or functionalitynotebookon-testplanplan-itemVS Code - planned item for upcomingVS Code - planned item for upcomingwebviewWebview issuesWebview issuesworkbench-auxwindowIssues related to use of auxiliary ("floating") windows.Issues related to use of auxiliary ("floating") windows.
Milestone
Description
With floating windows, users have the desire to move editors out of the main window into the child window. Some of our editors use an absolute positioned iframe
element that is resized and moved to fit into the editor area it belongs to. This will not work anymore as soon as the editor moves out of the window.
I already made a pass and configured currently unsupported editors with the new AuxWindowUnsupported
capability.
This impacts custom editors as well as notebooks.
Steps to move an editor out to a floating window:
- remove the
AuxWindowUnsupported
capability for the editor of choice - open such an editor
- trigger the "Move active editor into a new window" action from the command palette
//cc @Tyriar
stephenkraemer, Zwatotem, cweijan, zeel01, T-256 and 6 more
Metadata
Metadata
Labels
custom-editorsCustom editor API (webview based editors)Custom editor API (webview based editors)feature-requestRequest for new features or functionalityRequest for new features or functionalitynotebookon-testplanplan-itemVS Code - planned item for upcomingVS Code - planned item for upcomingwebviewWebview issuesWebview issuesworkbench-auxwindowIssues related to use of auxiliary ("floating") windows.Issues related to use of auxiliary ("floating") windows.