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

Terminal will not show completely in fullscreen mode when i use two monitors. #5505

New Issue
Closed
opened 2026-01-31 00:14:57 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 00:14:57 +00:00
Owner
Copy Link

Originally created by @CannedFish on GitHub (Dec 11, 2019).

Environment

Windows build number: Microsoft Windows  10.0.18362.476
Windows Terminal version (if applicable): 0.7.3382.0

Steps to reproduce

Toggle into fullscreen mode.

Expected behavior

The terminal enters into fullscreen mode without any tabs, no matter how many monitors used.
If I configure to use all monitors, it should show on all monitors.
On the other way, if I set to use only one monitor, it should show completely on the original monitor.

Actual behavior

The terminal entered into fullscreen mode without any tabs, but not complete with two monitors.
Half of terminal will show in the original monitor's screen, and the other will not show.

image
image

Originally created by @CannedFish on GitHub (Dec 11, 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 ```none Windows build number: Microsoft Windows 10.0.18362.476 Windows Terminal version (if applicable): 0.7.3382.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Toggle into fullscreen mode. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The terminal enters into fullscreen mode without any tabs, no matter how many monitors used. If I configure to use all monitors, it should show on all monitors. On the other way, if I set to use only one monitor, it should show completely on the original monitor. # Actual behavior <!-- What's actually happening? --> The terminal entered into fullscreen mode without any tabs, but not complete with two monitors. Half of terminal will show in the original monitor's screen, and the other will not show. ![image](https://user-images.githubusercontent.com/4979748/70607246-0886ff80-1c39-11ea-8006-2e04f4c38e8c.png) ![image](https://user-images.githubusercontent.com/4979748/70607319-2f453600-1c39-11ea-929f-057c45d2077e.png)
claunia added the Resolution-DuplicateProduct-Terminal labels 2026-01-31 00:14:57 +00:00
claunia commented 2026-01-31 00:14:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 11, 2019):

Huh. I guess that's correct, we don't expand to fill all the available monitors - we only take up the monitor the window is on.

Is there any application where fullscreen mode fills all the available monitors?

I'd think that supporting this style of fullscreen-ing would be incredibly challenging, since the window wouldn't necessarily have a rectangular bounds anymore. Instead, the window would be two rectangular regions (or N regions for N monitors).

@zadjii-msft commented on GitHub (Dec 11, 2019): Huh. I guess that's correct, we don't expand to fill all the available monitors - we only take up the monitor the window is on. Is there any application where fullscreen mode fills all the available monitors? I'd think that supporting this style of fullscreen-ing would be incredibly challenging, since the window wouldn't necessarily have a rectangular bounds anymore. Instead, the window would be two rectangular regions (or N regions for N monitors).
claunia commented 2026-01-31 00:14:58 +00:00
Author
Owner
Copy Link

@CannedFish commented on GitHub (Dec 11, 2019):

@zadjii-msft Thanks for replying.

Actually what I concern is that terminal now seems recognize two monitors already but only show contents on one. That causes me losing information in fullscreen mode.

@CannedFish commented on GitHub (Dec 11, 2019): @zadjii-msft Thanks for replying. Actually what I concern is that terminal now seems recognize two monitors already but only show contents on one. That causes me losing information in fullscreen mode.
claunia commented 2026-01-31 00:14:59 +00:00
Author
Owner
Copy Link

@kid1412621 commented on GitHub (Dec 12, 2019):

same here
image

@kid1412621 commented on GitHub (Dec 12, 2019): same here ![image](https://user-images.githubusercontent.com/26278054/70716799-03ed4480-1d28-11ea-8478-e75482dfbbf6.png)
claunia commented 2026-01-31 00:14:59 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 12, 2019):

This looks like a /dupe of #3710. There's an open pull request #3721 we're evaluating that may help this (and it looks like it solves the buffer size issue where terminal thinks it can put stuff off on your other monitor but not display it.)

@DHowett-MSFT commented on GitHub (Dec 12, 2019): This looks like a /dupe of #3710. There's an open pull request #3721 we're evaluating that may help this (and it looks like it solves the buffer size issue where terminal thinks it can put stuff off on your other monitor but not display it.)
claunia commented 2026-01-31 00:14:59 +00:00
Author
Owner
Copy Link

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

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Dec 12, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Product-Terminal Resolution-Duplicate
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#5505
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?