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

Full Screen issues with Panes Open? #5187

New Issue
Closed
opened 2026-01-31 00:06:59 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 00:06:59 +00:00
Owner
Copy Link

Originally created by @OmriSama on GitHub (Nov 26, 2019).

Environment

Windows build number: 10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable): 0.7.3291.0

Any other software?: Connected via OpenSSH to an Ubuntu VM running locally. Using ZSH.

Bug

When going into the new full-screen mode, you can't see other panes. So my terminal will look like this:

image

But then in full-screen mode like this:

image

And the other panes are still there, and I can move focus to them, but not actually see them.

edit: moved this second bit to #3709

I apologize ahead of time if this is already documented, or is not a completed feature/duplicate issue.

Originally created by @OmriSama on GitHub (Nov 26, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment **Windows build number**: 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 **Windows Terminal version (if applicable)**: 0.7.3291.0 **Any other software?**: Connected via OpenSSH to an Ubuntu VM running locally. Using ZSH. # Bug When going into the new full-screen mode, you can't see other panes. So my terminal will look like this: ![image](https://user-images.githubusercontent.com/10534779/69660591-82ae6600-1035-11ea-8b05-a43910b01797.png) But then in full-screen mode like this: ![image](https://user-images.githubusercontent.com/10534779/69660431-29463700-1035-11ea-9980-fa80b34c067f.png) And the other panes are still there, and I can move focus to them, but not actually see them. --- _edit: moved this second bit to #3709_ <!-- *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) --> I apologize ahead of time if this is already documented, or is not a completed feature/duplicate issue.
claunia commented 2026-01-31 00:07:02 +00:00
Author
Owner
Copy Link

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

Does a Full Screen window behave differently to a normal window? In terms of reporting it's size?

@mdtauk commented on GitHub (Nov 26, 2019): Does a Full Screen window behave differently to a normal window? In terms of reporting it's size?
claunia commented 2026-01-31 00:07:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 26, 2019):

@OmriSama Well that's certainly odd. For the sake of keeping discussion simple, I'm going to focus on just that first issue in this thread, and track the "fullscreen from maximized doesn't work" in #3709.

I'm unfortunately not seeing that behavior myself, so we'll need to find what causes that to repro... If you navigate to the other pane when it's in the broken state, does typing text appear where the pane should be?

Does it only occur with that Profile?

@zadjii-msft commented on GitHub (Nov 26, 2019): @OmriSama Well that's certainly odd. For the sake of keeping discussion simple, I'm going to focus on just that first issue in this thread, and track the "fullscreen from maximized doesn't work" in #3709. I'm unfortunately not seeing that behavior myself, so we'll need to find what causes that to repro... If you navigate to the other pane when it's in the broken state, does typing text appear where the pane should be? Does it only occur with that Profile?
claunia commented 2026-01-31 00:07:03 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 6, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Dec 6, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 00:07:04 +00:00
Author
Owner
Copy Link

@OmriSama commented on GitHub (Dec 10, 2019):

Just checked again and this specific issue seems to have been fixed with the latest release. Cheers!

EDIT: Nevermind. It works fine on my computer at home which uses the latest Insider (Fast Ring) builds, but not on my work computer which is on 18363.476 at the moment (also the computer that I posted about this issue from).

@OmriSama commented on GitHub (Dec 10, 2019): Just checked again and this specific issue seems to have been fixed with the latest release. Cheers! **EDIT**: Nevermind. It works fine on my computer at home which uses the latest Insider (Fast Ring) builds, but not on my work computer which is on 18363.476 at the moment (also the computer that I posted about this issue from).
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 Needs-Attention Needs-Repro Needs-Tag-Fix Priority-3 Product-Terminal
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#5187
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?