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

Entering Fullscreen from Maximized doesn't work right #5193

New Issue
Closed
opened 2026-01-31 00:07:13 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 00:07:13 +00:00
Owner
Copy Link

Originally created by @zadjii-msft on GitHub (Nov 26, 2019).

Moved from #3707

Environment

Windows build number: 10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable): 0.7.3291.0

Another behavior is that when going into Full-Screen mode from a maximized window, you still see the taskbar and the padding around the shell looks all messed up:

image

fullscreens to:

image

Originally created by @zadjii-msft on GitHub (Nov 26, 2019). ###### Moved from #3707 # Environment **Windows build number**: 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 **Windows Terminal version (if applicable)**: 0.7.3291.0 *Another behavior* is that when going into Full-Screen mode from a maximized window, you still see the taskbar and the padding around the shell looks all messed up: ![image](https://user-images.githubusercontent.com/10534779/69660521-60b4e380-1035-11ea-824b-8bf2339c4567.png) fullscreens to: ![image](https://user-images.githubusercontent.com/10534779/69660545-6ad6e200-1035-11ea-8590-69d579ec3c1f.png)
claunia commented 2026-01-31 00:07:15 +00:00
Author
Owner
Copy Link

@OmriSama commented on GitHub (Nov 26, 2019):

Thanks @zadjii-msft !

@OmriSama commented on GitHub (Nov 26, 2019): Thanks @zadjii-msft !
claunia commented 2026-01-31 00:07:15 +00:00
Author
Owner
Copy Link

@OmriSama commented on GitHub (Nov 26, 2019):

I should also mention that I use three monitors at work, and my 4k monitor (my third, as opposed to the other two being 1080p) displays a different behavior when fullscreening:

Not maximized -> fullscreen:
image

Maximized -> fullscreen:
image

@OmriSama commented on GitHub (Nov 26, 2019): I should also mention that I use three monitors at work, and my 4k monitor (my third, as opposed to the other two being 1080p) displays a different behavior when fullscreening: Not maximized -> fullscreen: ![image](https://user-images.githubusercontent.com/10534779/69661977-4b8d8400-1038-11ea-817c-f02103a0561c.png) Maximized -> fullscreen: ![image](https://user-images.githubusercontent.com/10534779/69662014-6102ae00-1038-11ea-8dc6-9b98293ab8ec.png)
claunia commented 2026-01-31 00:07:15 +00:00
Author
Owner
Copy Link

@shanselman commented on GitHub (Nov 26, 2019):

Yep, I hit this within minutes. :(

@shanselman commented on GitHub (Nov 26, 2019): Yep, I hit this within minutes. :(
claunia commented 2026-01-31 00:07:15 +00:00
Author
Owner
Copy Link

@nicolaskeller commented on GitHub (Nov 27, 2019):

Fullscreen looks good if padding is set to 8,8,8,8.
If padding is set to 0,0,0,0 the content gets cut.

@nicolaskeller commented on GitHub (Nov 27, 2019): Fullscreen looks good if padding is set to 8,8,8,8. If padding is set to 0,0,0,0 the content gets cut.
claunia commented 2026-01-31 00:07:15 +00:00
Author
Owner
Copy Link

@nathpete-msft commented on GitHub (Dec 6, 2019):

Interestingly, this issue (including the 4k monitor issue mentioned by @OmriSama) only repros for me if I have showTabsInTitlebar enabled. With that setting off switching to fullscreen works as expected regardless of the starting window state or the monitor it's on.

@nathpete-msft commented on GitHub (Dec 6, 2019): Interestingly, this issue (including the 4k monitor issue mentioned by @OmriSama) _only_ repros for me if I have `showTabsInTitlebar` enabled. With that setting off switching to fullscreen works as expected regardless of the starting window state or the monitor it's on.
claunia commented 2026-01-31 00:07:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 14, 2020):

:tada:This issue was addressed in #3721, which has now been successfully released as Windows Terminal Preview v0.8.10091.0.🎉

Handy links:

@ghost commented on GitHub (Jan 14, 2020): :tada:This issue was addressed in #3721, which has now been successfully released as `Windows Terminal Preview v0.8.10091.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.8.10091.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
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-UserInterface Issue-Bug Priority-3 Product-Terminal Resolution-Fix-Committed
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#5193
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?