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

Could not disable transparency, transparency only in effect when active #17478

New Issue
Open
opened 2026-01-31 05:43:43 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:43:43 +00:00
Owner
Copy Link

Originally created by @JasonGoemaat on GitHub (May 15, 2022).

Windows Terminal version

1.12.10982.0

Windows build number

10.0.19043.0

Other Software

No response

Steps to reproduce

Open windows terminal

Expected Behavior

Window is opaque

Actual Behavior

Window is transparent when active, opaque when not.

This is so annoying. I probably spent hours over multiple occasions trying different combinations of running terminal as administrator or not and fiddling with appearance settings to get rid of the transparency, saving, and restarting, but nothing worked. Finally searching for transparency bugs here I found one mentioning CTRL+SHIFT+MOUSEWHEEL saying it no longer worked. That actually DOES work for me, however it resets to transparent every time I start a new instance of windows terminal. Now that's one more thing cluttering up my mind.

Ok, I found looking at the JSON file that I had my default terminal's useAcrylic set to true. I had no idea what that setting was for and still don't understand it. I don't know why I ever would have set it myself.

Playing around with it more it looks like setting any level of 'Background opacity' other than 100%, it enables acrylic. I suppose I might have done that in the past. But when I change the opacity back to 100%, useAcrylic remains checked and the window remains transparent. If you set opacity to 100% I think it should disable useAcrylic.

Originally created by @JasonGoemaat on GitHub (May 15, 2022). ### Windows Terminal version 1.12.10982.0 ### Windows build number 10.0.19043.0 ### Other Software _No response_ ### Steps to reproduce Open windows terminal ### Expected Behavior Window is opaque ### Actual Behavior Window is transparent when active, opaque when not. This is so annoying. I probably spent hours over multiple occasions trying different combinations of running terminal as administrator or not and fiddling with appearance settings to get rid of the transparency, saving, and restarting, but nothing worked. Finally searching for transparency bugs here I found one mentioning CTRL+SHIFT+MOUSEWHEEL saying it no longer worked. That actually DOES work for me, however it resets to transparent every time I start a new instance of windows terminal. Now that's one more thing cluttering up my mind. Ok, I found looking at the JSON file that I had my default terminal's useAcrylic set to true. I had no idea what that setting was for and still don't understand it. I don't know why I ever would have set it myself. Playing around with it more it looks like setting any level of 'Background opacity' other than 100%, it enables acrylic. I suppose I might have done that in the past. But when I change the opacity back to 100%, useAcrylic remains checked and the window remains transparent. If you set opacity to 100% I think it should disable useAcrylic.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:43:43 +00:00
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 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#17478
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?