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

Drop-down context menu changes to inactive color scheme after right-click context menu is opened #21273

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

Originally created by @digitalguy99 on GitHub (Feb 19, 2024).

Windows Terminal version

1.19.10302.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

Here are the steps I went through that triggered the bug:

  1. I set experimental.rightClickContextMenu to true and saved the settings.json file
  2. I restarted my Windows Terminal
  3. I right clicked to open the right-click context menu
  4. I then pressed the new tab dropdown to open the dropdown context menu

Here's a gif that illustrates what I did:
202402191126

Expected Behavior

The color of the dropdown context menu should not change to its inactive color scheme.

Actual Behavior

The color of the dropdown context menu changed to its inactive color scheme.

Originally created by @digitalguy99 on GitHub (Feb 19, 2024). ### Windows Terminal version 1.19.10302.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce Here are the steps I went through that triggered the bug: 1. I set `experimental.rightClickContextMenu` to true and saved the settings.json file 2. I restarted my Windows Terminal 3. I right clicked to open the right-click context menu 4. I then pressed the new tab dropdown to open the dropdown context menu Here's a gif that illustrates what I did: ![202402191126](https://github.com/microsoft/terminal/assets/52367722/f22828ad-bb99-40e6-91a2-97eac2fd3ac6) ### Expected Behavior The color of the dropdown context menu should not change to its inactive color scheme. ### Actual Behavior The color of the dropdown context menu changed to its inactive color scheme.
claunia added the Issue-BugResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 07:38:19 +00:00
claunia commented 2026-01-31 07:38:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 19, 2024):

This looks basically exactly the same as #7532. There was a bug in the OS that caused some shadows to be at the wrong z-order. I believe that's fixed in OS builds >=22000. Thanks!

/dup https://task.ms/33411893

@zadjii-msft commented on GitHub (Feb 19, 2024): This looks basically exactly the same as #7532. There was a bug in the OS that caused some shadows to be at the wrong z-order. I believe that's fixed in OS builds >=22000. Thanks! /dup https://task.ms/33411893
claunia commented 2026-01-31 07:38:21 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 19, 2024):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Feb 19, 2024): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
claunia commented 2026-01-31 07:38:21 +00:00
Author
Owner
Copy Link

@digitalguy99 commented on GitHub (Feb 20, 2024):

This looks basically exactly the same as #7532. There was a bug in the OS that caused some shadows to be at the wrong z-order. I believe that's fixed in OS builds >=22000. Thanks!

/dup https://task.ms/33411893

@zadjii-msft I'm aware that for Win 11 users they can simply update to the newest build. But is there a solution for Windows 10 users?

@digitalguy99 commented on GitHub (Feb 20, 2024): > This looks basically exactly the same as #7532. There was a bug in the OS that caused some shadows to be at the wrong z-order. I believe that's fixed in OS builds >=22000. Thanks! > > /dup https://task.ms/33411893 @zadjii-msft I'm aware that for Win 11 users they can simply update to the newest build. But is there a solution for Windows 10 users?
claunia commented 2026-01-31 07:38:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 20, 2024):

Alas, not that I'm aware of. There was a huge pile of bugfixes for XAML in the Windows 10->11 era, but IIRC this one was more like a bug that got accidentally fixed by a new OS feature, and that feature would have a hard time getting backported. Sorry about that 😕

@zadjii-msft commented on GitHub (Feb 20, 2024): Alas, not that I'm aware of. There was a huge pile of bugfixes for XAML in the Windows 10->11 era, but IIRC this one was more like a bug that got accidentally fixed by a new OS feature, and that feature would have a hard time getting backported. Sorry about that 😕
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 Issue-Bug Needs-Tag-Fix Resolution-External
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#21273
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?