starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-04-25 23:52:52 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Exiting from Full Screen mode incorrectly restores window size #522

New Issue
Open
opened 2026-01-30 21:54:16 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 21:54:16 +00:00
Owner
Copy Link

Originally created by @alabuzhev on GitHub (Jan 17, 2019).

Version 10.0.17763.253

Start cmd.exe
Enter command mode 80, 25
Go to window menu - Properties - Layout
Check that Window Size is 80 x 25 indeed
Close Properties
Press Alt+Enter twice to enter and exit full screen
Go to window menu - Properties - Layout
Check Window Size again. This time it's not 80 x 25, but 78 x 24.

This happens because exiting full screen restores the original outer window size (with the title, borders etc., say, 802 x 532px), however:

  • Entering full screen increases the buffer size (which is fine)
  • Exiting full screen doesn't change the buffer size (which is also fine)
  • The console window now has to display scrollbars (also fine), but since it's outer size is the same it has to display them at the expense of console viewport area.

This causes an issue in an app that automatically syncs buffer size with window size - after every switch to full screen and back window size gets smaller, the app reduces the buffer size accordingly, eventually going down to nothing.
Also, even if an app doesn't do anything like that, reducing the viewport size can make some (potentially important) information invisible.

Please consider preserving the console viewport size and increasing the outer window size to make room for scrollbars.

Originally created by @alabuzhev on GitHub (Jan 17, 2019). Version 10.0.17763.253 Start cmd.exe Enter command `mode 80, 25` Go to window menu - Properties - Layout Check that Window Size is 80 x 25 indeed Close Properties Press Alt+Enter twice to enter and exit full screen Go to window menu - Properties - Layout Check Window Size again. This time it's not 80 x 25, but 78 x 24. This happens because exiting full screen restores the original **outer** window size (with the title, borders etc., say, 802 x 532px), however: - Entering full screen increases the buffer size (which is fine) - Exiting full screen doesn't change the buffer size (which is also fine) - The console window now has to display scrollbars (also fine), but since it's outer size is the same it has to display them at the expense of console viewport area. This causes an issue in an app that automatically syncs buffer size with window size - after every switch to full screen and back window size gets smaller, the app reduces the buffer size accordingly, eventually going down to nothing. Also, even if an app doesn't do anything like that, reducing the viewport size can make some (potentially important) information invisible. Please consider preserving the console viewport size and increasing the outer window size to make room for scrollbars.
claunia commented 2026-01-30 21:54:17 +00:00
Author
Owner
Copy Link

@boomsya commented on GitHub (Jan 18, 2019):

the same bug in Far 3 when exit from full screen mode
win 10 x64 1709.16299.309

@boomsya commented on GitHub (Jan 18, 2019): the same bug in Far 3 when exit from full screen mode win 10 x64 1709.16299.309
claunia commented 2026-01-30 21:54:17 +00:00
Author
Owner
Copy Link

@Riju-bak commented on GitHub (Jun 16, 2023):

Is anyone working on this? If not, can I try to fix it?

@Riju-bak commented on GitHub (Jun 16, 2023): Is anyone working on this? If not, can I try to fix it?
claunia commented 2026-01-30 21:54:17 +00:00
Author
Owner
Copy Link

@m3dbedb commented on GitHub (Sep 21, 2023):

How to exit full screen in FAR?

@m3dbedb commented on GitHub (Sep 21, 2023): How to exit full screen in FAR?
claunia commented 2026-01-30 21:54:18 +00:00
Author
Owner
Copy Link

@boomsya commented on GitHub (Sep 21, 2023):

alt+enter

@boomsya commented on GitHub (Sep 21, 2023): alt+enter
claunia commented 2026-01-30 21:54:18 +00:00
Author
Owner
Copy Link

@raman118 commented on GitHub (Aug 17, 2025):

Hi, I'm a new contributor and would like to work on this issue. Please let me know if it's okay to proceed.

@raman118 commented on GitHub (Aug 17, 2025): Hi, I'm a new contributor and would like to work on this issue. Please let me know if it's okay to proceed.
claunia commented 2026-01-30 21:54:18 +00:00
Author
Owner
Copy Link

@shivam-dhir commented on GitHub (Jan 22, 2026):

Hi, I would love to work on this issue

@shivam-dhir commented on GitHub (Jan 22, 2026): Hi, I would love to work on this issue
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Interaction good first issue Help Wanted Issue-Bug Priority-3 Product-Conhost
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#522
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?