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

Quake mode drop-down doesn't handle SPI_SETWORKAREA #20581

New Issue
Open
opened 2026-01-31 07:18:18 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 07:18:18 +00:00
Owner
Copy Link

Originally created by @sharunkumar on GitHub (Sep 29, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

  • Open windows Copilot preview while quake mode is open
  • Close Windows Copilot
  • Open / Close Quake mode using the hotkey (win+`)

Expected Behavior

No response

Actual Behavior

Screenshot

Screenshot

Originally created by @sharunkumar on GitHub (Sep 29, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.22621.0 ### Other Software _No response_ ### Steps to reproduce - Open windows Copilot preview while quake mode is open - Close Windows Copilot - Open / Close Quake mode using the hotkey (win+`) ### Expected Behavior _No response_ ### Actual Behavior ![Screenshot](https://github.com/microsoft/terminal/assets/715417/cbc48fe6-7030-45dd-9207-5411968cd8c0) ![Screenshot](https://github.com/microsoft/terminal/assets/715417/dfa52c85-8387-4f11-9a2b-fd11c5dd4beb)
claunia added the Help WantedIssue-BugProduct-TerminalArea-Windowing labels 2026-01-31 07:18:19 +00:00
claunia commented 2026-01-31 07:18:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 5, 2023):

Yep, this is real. MSFT:46421646 internally.

Looks like Copilot is changing the work area. Apparently as part of the design, when the work area changes back to the original1 , Windows doesn't resize apps back. From the thread, this seems like a good design.

We need to listen for WM_SETTINGCHANGE where wparam = SPI_SETWORKAREA, and use that to recalculate our snapped size. Shouldn't be too hard.

  1. grows in size? It's unclear what exactly the difference in the shrink vs grow is ↩︎

@zadjii-msft commented on GitHub (Oct 5, 2023): Yep, this is real. MSFT:46421646 internally. Looks like Copilot is changing the work area. Apparently as part of the design, when the work area changes _back_ to the original[^1], Windows doesn't resize apps back. From the thread, this seems like a good design. We need to listen for `WM_SETTINGCHANGE` where `wparam = SPI_SETWORKAREA`, and use that to recalculate our snapped size. Shouldn't be too hard. [^1]: grows in size? It's unclear what exactly the difference in the shrink vs grow is
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-Windowing Help Wanted Issue-Bug 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#20581
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?