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

100% focused opacity interferes with unfocused opacity #19099

New Issue
Open
opened 2026-01-31 06:33:42 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:33:42 +00:00
Owner
Copy Link

Originally created by @jtheuerkauf on GitHub (Dec 19, 2022).

When window opacity while focused is set to 100%, the background while unfocused doesn't follow the Unfocused Appearance settings:
image
Some extra padding allows you to see that the background is there, but the command window is opaque.

As soon as opacity is less than 100%, the background behaves as expected while unfocused:
image

It doesn't matter what profile is used (note the displayed settings are defaults) - even when the settings are applied to individual profiles the behavior is the same.

I'll provide whatever other info I can, just let me know what's needed.
image

Originally created by @jtheuerkauf on GitHub (Dec 19, 2022). When window opacity while focused is set to 100%, the background while unfocused doesn't follow the Unfocused Appearance settings: ![image](https://user-images.githubusercontent.com/105436210/208339864-2c6cfe49-313e-4f5c-a4f3-8d408d54fc2b.png) Some extra padding allows you to see that the background is there, but the command window is opaque. As soon as opacity is less than 100%, the background behaves as expected while unfocused: ![image](https://user-images.githubusercontent.com/105436210/208339492-60cd869a-165e-4f64-aca2-0640920db0df.png) It doesn't matter what profile is used (note the displayed settings are defaults) - even when the settings are applied to individual profiles the behavior is the same. I'll provide whatever other info I can, just let me know what's needed. ![image](https://user-images.githubusercontent.com/105436210/208340281-d06a7c04-0de3-402c-b56c-fcc3755ef981.png)
claunia added the Issue-BugPriority-3Product-TerminalArea-TerminalControl labels 2026-01-31 06:33:42 +00:00
claunia commented 2026-01-31 06:33:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 19, 2022):

You know, I think I've seen this too with Atlas enabled, even without an unfocused appearance. I think I've been able to make it happen a couple times with just the "set opacity" actions.

Thanks for filing! We'll make sure to take a look ☺️

@zadjii-msft commented on GitHub (Dec 19, 2022): You know, I think I've seen this too with Atlas enabled, even without an unfocused appearance. I think I've been able to make it happen a couple times with just the "set opacity" actions. Thanks for filing! We'll make sure to take a look ☺️
claunia commented 2026-01-31 06:33:43 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Jan 12, 2023):

Can confirm that this issue no longer repros if you disable atlas engine rendering and restart WT. Investigating further.

Further updates:

  • This does not repro if you have a background image for both appearances (doesn't need to be the same image, you just need to have a bg image in each appearance)
@PankajBhojwani commented on GitHub (Jan 12, 2023): Can confirm that this issue no longer repros if you disable atlas engine rendering and restart WT. Investigating further. Further updates: - This does not repro if you have a background image for _both_ appearances (doesn't need to be the same image, you just need to have _a_ bg image in each appearance)
claunia commented 2026-01-31 06:33:43 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 13, 2023):

@PankajBhojwani If this is atlas-only, we can punt it out of 1.17. It's not going to be enabled by default until later.

@DHowett commented on GitHub (Jan 13, 2023): @PankajBhojwani If this is atlas-only, we can punt it out of 1.17. It's not going to be enabled by default until later.
claunia commented 2026-01-31 06:33:43 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Jan 13, 2023):

Sounds good, punting to 1.18 for now.

@PankajBhojwani commented on GitHub (Jan 13, 2023): Sounds good, punting to 1.18 for now.
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-TerminalControl Issue-Bug Priority-3 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#19099
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?