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

Shortcut keys to fullscreen window cause unexpected behavior on second monitor #5434

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

Originally created by @DukeOfEtiquette on GitHub (Dec 6, 2019).

Environment

Windows build number: 
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19033.0 Microsoft Windows NT 10.0.19033.0


Windows Terminal version (if applicable):
0.7.3382.0


Any other software?
Nope.

Steps to reproduce

  1. Launch terminal
  2. Move terminal window to second monitor/screen
  3. Press with F11 or alt+enter
  4. Gives an unworkable black screen in fullscreen

Expected behavior

Full screen with normal styling and interaction

Actual behavior

Black screen that seems to be non-interactive.
win_terminal_fullscreen

I fullscreen twice on each monitor, using the F11 and alt+enter once on each monitor.

Note

As well, the Terminal window ALWAYS launches from monitor 1, and does not remember it was closed in monitor 2. Since I always run my terminal on monitor 2, this is a slight annoyance.

Originally created by @DukeOfEtiquette on GitHub (Dec 6, 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: Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.19033.0 Microsoft Windows NT 10.0.19033.0 Windows Terminal version (if applicable): 0.7.3382.0 Any other software? Nope. ``` # Steps to reproduce 1. Launch terminal 2. Move terminal window to second monitor/screen 3. Press with F11 or alt+enter 4. Gives an unworkable black screen in fullscreen # Expected behavior Full screen with normal styling and interaction # Actual behavior Black screen that seems to be non-interactive. ![win_terminal_fullscreen](https://user-images.githubusercontent.com/8975234/70343839-1e498e80-180d-11ea-85cf-78243b3d1ba9.gif) I fullscreen twice on each monitor, using the F11 and alt+enter once on each monitor. # Note As well, the Terminal window ALWAYS launches from monitor 1, and does not remember it was closed in monitor 2. Since I always run my terminal on monitor 2, this is a slight annoyance.
claunia added the Resolution-Duplicate label 2026-01-31 00:13:12 +00:00
claunia commented 2026-01-31 00:13:13 +00:00
Author
Owner
Copy Link

@gerhardamegg commented on GitHub (Dec 8, 2019):

Same on Microsoft Windows [Version 10.0.18363.476]: Works as expected on primary screen, is buggy on secondary. Copy of #3710

@gerhardamegg commented on GitHub (Dec 8, 2019): Same on `Microsoft Windows [Version 10.0.18363.476]`: Works as expected on primary screen, is buggy on secondary. Copy of [#3710](https://github.com/microsoft/terminal/issues/3710)
claunia commented 2026-01-31 00:13:13 +00:00
Author
Owner
Copy Link

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

Thanks for the report and the gif to demonstrate it! Looks to me like this is a /dup of #3710, so I'll direct discussion to that thread. Thanks!

@zadjii-msft commented on GitHub (Dec 9, 2019): Thanks for the report and the gif to demonstrate it! Looks to me like this is a /dup of #3710, so I'll direct discussion to that thread. Thanks!
claunia commented 2026-01-31 00:13:14 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 9, 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 9, 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 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#5434
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?