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

Windows Terminal title bar non clickable/interactable #9436

New Issue
Closed
opened 2026-01-31 01:54:28 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 01:54:28 +00:00
Owner
Copy Link

Originally created by @Sov3rain on GitHub (Jul 4, 2020).

Environment

Microsoft Windows [Version 10.0.18363.900]
Windows Terminal 1.0.1811.0

Steps to reproduce

  1. Open terminal

Expected behavior

I should be able to use the buttons on the title bar to close / expand / reduce the app, or even add new tabs.

Actual behavior

Buttons are "dead", they don't receive clicks.

Originally created by @Sov3rain on GitHub (Jul 4, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Microsoft Windows [Version 10.0.18363.900] Windows Terminal 1.0.1811.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open terminal # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> I should be able to use the buttons on the title bar to close / expand / reduce the app, or even add new tabs. # Actual behavior <!-- What's actually happening? --> Buttons are "dead", they don't receive clicks.
claunia added the Resolution-DuplicateProduct-Terminal labels 2026-01-31 01:54:28 +00:00
claunia commented 2026-01-31 01:54:29 +00:00
Author
Owner
Copy Link

@Neo-Desktop commented on GitHub (Jul 4, 2020):

Environment

Microsoft Windows [Version 10.0.19041.264]
Windows Terminal 1.0.1811.0

I have the same issues as described in https://github.com/microsoft/terminal/issues/6784#issue-650885581
Furthermore, I am unable to select/copy text.
It seems that the terminal is not responding to mouse input at all
The hover color change events for the UI buttons ( new tab, close tab, tab menu, minimize, maximize, exit ) do not fire when in the error state

I have also confirmed the same behavior on Windows Terminal Preview v1.1.1812.0

Restarting the computer fixes the issue in both builds.

@Neo-Desktop commented on GitHub (Jul 4, 2020): ### Environment ``` Microsoft Windows [Version 10.0.19041.264] Windows Terminal 1.0.1811.0 ``` I have the same issues as described in https://github.com/microsoft/terminal/issues/6784#issue-650885581 Furthermore, I am unable to select/copy text. It seems that the terminal is not responding to mouse input at all The hover color change events for the UI buttons ( new tab, close tab, tab menu, minimize, maximize, exit ) do not fire when in the error state I have also confirmed the same behavior on `Windows Terminal Preview v1.1.1812.0` Restarting the computer fixes the issue in both builds.
claunia commented 2026-01-31 01:54:29 +00:00
Author
Owner
Copy Link

@Sov3rain commented on GitHub (Jul 5, 2020):

Environment

Microsoft Windows [Version 10.0.19041.264]
Windows Terminal 1.0.1811.0

I have the same issues as described in #6784 (comment)
Furthermore, I am unable to select/copy text.
It seems that the terminal is not responding to mouse input at all
The hover color change events for the UI buttons ( new tab, close tab, tab menu, minimize, maximize, exit ) do not fire when in the error state

I have also confirmed the same behavior on Windows Terminal Preview v1.1.1812.0

Restarting the computer fixes the issue in both builds.

I did not try with the Preview, but restarting seems to fix the bug for now.

@Sov3rain commented on GitHub (Jul 5, 2020): > ### Environment > ``` > Microsoft Windows [Version 10.0.19041.264] > Windows Terminal 1.0.1811.0 > ``` > > I have the same issues as described in [#6784 (comment)](https://github.com/microsoft/terminal/issues/6784#issue-650885581) > Furthermore, I am unable to select/copy text. > It seems that the terminal is not responding to mouse input at all > The hover color change events for the UI buttons ( new tab, close tab, tab menu, minimize, maximize, exit ) do not fire when in the error state > > I have also confirmed the same behavior on `Windows Terminal Preview v1.1.1812.0` > > Restarting the computer fixes the issue in both builds. I did not try with the Preview, but restarting seems to fix the bug for now.
claunia commented 2026-01-31 01:54:29 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Jul 5, 2020):

https://github.com/microsoft/terminal/issues/6120 describes similar symptoms.

@KalleOlaviNiemitalo commented on GitHub (Jul 5, 2020): <https://github.com/microsoft/terminal/issues/6120> describes similar symptoms.
claunia commented 2026-01-31 01:54:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 6, 2020):

@Sov3rain Are you using PowerToys at all? If so:

  • Are you using the Terminal on a high DPI display?
    • If so, and if possible, does dragging the window to a 100% scaling display magically restore mouse functionality to the Terminal?
  • Similarly, are you using the Terminal on your primary display?
    • If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal?
  • Does the PowerToys settings app similarly not respond to mouse input?
  • Do you have the Shortcut Guide enabled in PowerToys?
    • If so, does it actually work if you long press Win?
  • By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)?

If you're experiencing this, and you can interact with the PowerToys settings app (you might need to drag it to another monitor), then

  • can you fix the issue by disabling "Shortcut Guide" in PowerToys?
@zadjii-msft commented on GitHub (Jul 6, 2020): @Sov3rain Are you using PowerToys at all? If so: * Are you using the Terminal on a high DPI display? - If so, and if possible, does dragging the window to a 100% scaling display magically restore mouse functionality to the Terminal? * Similarly, are you using the Terminal on your primary display? - If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal? * Does the PowerToys settings app similarly not respond to mouse input? * Do you have the Shortcut Guide enabled in PowerToys? - If so, does it actually work if you long press <kbd>Win</kbd>? * By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)? If you're experiencing this, and you can interact with the PowerToys settings app (you might need to drag it to another monitor), then * can you fix the issue by disabling "Shortcut Guide" in PowerToys?
claunia commented 2026-01-31 01:54:29 +00:00
Author
Owner
Copy Link

@Sov3rain commented on GitHub (Jul 8, 2020):

@zadjii-msft

Are you using PowerToys at all?

Yes I do.

  • Are you using the Terminal on a high DPI display?

No, just a regular full HD 1080p monitor.

  • Similarly, are you using the Terminal on your primary display?

I only got one display.

  • If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal?
  • Does the PowerToys settings app similarly not respond to mouse input?

I didn't encounter the bug again for now, I'll try that if it goes wrong.

  • Do you have the Shortcut Guide enabled in PowerToys?

Yes I do.

  • If so, does it actually work if you long press Win?

Yes it does.

  • By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)?

No I didn't.

If you're experiencing this, and you can interact with the PowerToys settings app (you might need to drag it to another monitor), then

  • can you fix the issue by disabling "Shortcut Guide" in PowerToys?

As I said, I didn't encounter the issue again in my recent use of the terminal. I'll let you know if it happens again.

@Sov3rain commented on GitHub (Jul 8, 2020): @zadjii-msft >Are you using PowerToys at all? Yes I do. > * Are you using the Terminal on a high DPI display? No, just a regular full HD 1080p monitor. > * Similarly, are you using the Terminal on your primary display? I only got one display. > * If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal? > * Does the PowerToys settings app similarly not respond to mouse input? I didn't encounter the bug again for now, I'll try that if it goes wrong. > * Do you have the Shortcut Guide enabled in PowerToys? Yes I do. > * If so, does it actually work if you long press Win? Yes it does. > * By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)? No I didn't. > If you're experiencing this, and you can interact with the PowerToys settings app (you might need to drag it to another monitor), then > > * can you fix the issue by disabling "Shortcut Guide" in PowerToys? As I said, I didn't encounter the issue again in my recent use of the terminal. I'll let you know if it happens again.
claunia commented 2026-01-31 01:54:30 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 10, 2020):

Thanks for all the info. After all that, I'm gonna mark this as a /duplicate of #6120.
Cheers, all, and thanks for playing!

@DHowett commented on GitHub (Jul 10, 2020): Thanks for all the info. After all that, I'm gonna mark this as a /duplicate of #6120. Cheers, all, and thanks for playing!
claunia commented 2026-01-31 01:54:30 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 10, 2020):

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 (Jul 10, 2020): 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#9436
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?