-
Notifications
You must be signed in to change notification settings - Fork 39.7k
Native wayland support with newest electron #109176
Copy link
Copy link
Closed
Labels
electronIssues and items related to ElectronIssues and items related to Electroninsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsiderslinuxIssues with VS Code on LinuxIssues with VS Code on LinuxupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)upstream-issue-linkedThis is an upstream issue that has been reported upstreamThis is an upstream issue that has been reported upstream
Metadata
Metadata
Assignees
Labels
electronIssues and items related to ElectronIssues and items related to Electroninsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsiderslinuxIssues with VS Code on LinuxIssues with VS Code on LinuxupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)upstream-issue-linkedThis is an upstream issue that has been reported upstreamThis is an upstream issue that has been reported upstream
Native wayland support would be great to run vs code without XWayland as described in #77752.
Recently electron merged the chrome version with the ozone backend needed:
electron/electron#26022
This would allow for: