Before submitting
Area
apps/desktop
Steps to reproduce
- On GNOME, configure a custom window button layout, for example only a close button or controls on the left.
- Open T3 Code Desktop.
- Compare T3 Code's window controls with other system windows.
Expected behavior
T3 Code should respect the system-configured window button layout and placement.
For example, if GNOME is configured to show only the close button, T3 Code should do the same.
Actual behavior
T3 Code shows Electron's default Window Controls Overlay layout instead of the layout configured by the desktop environment.
This makes the title bar inconsistent with the rest of the desktop.
T3 Code already uses titleBarStyle: "hidden" with titleBarOverlay on Linux, but it currently uses Electron 41.5.0.
Electron 43 added support for system-configured button layouts in WCO on Linux:
electron/electron#51161
Updating Electron should allow T3 Code to inherit the user's Linux window control layout without replacing the existing custom title bar.
Impact
Cosmetic issue
Version or commit
No response
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
Before submitting
Area
apps/desktop
Steps to reproduce
Expected behavior
T3 Code should respect the system-configured window button layout and placement.
For example, if GNOME is configured to show only the close button, T3 Code should do the same.
Actual behavior
T3 Code shows Electron's default Window Controls Overlay layout instead of the layout configured by the desktop environment.
This makes the title bar inconsistent with the rest of the desktop.
T3 Code already uses titleBarStyle: "hidden" with titleBarOverlay on Linux, but it currently uses Electron 41.5.0.
Electron 43 added support for system-configured button layouts in WCO on Linux:
electron/electron#51161
Updating Electron should allow T3 Code to inherit the user's Linux window control layout without replacing the existing custom title bar.
Impact
Cosmetic issue
Version or commit
No response
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response