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

Opacity is not working; the terminal remains always opaque #1942

New Issue
Closed
opened 2026-01-30 22:42:30 +00:00 by claunia · 13 comments
claunia commented 2026-01-30 22:42:30 +00:00
Owner
Copy Link

Originally created by @TheBlueSky on GitHub (Jun 22, 2019).

Whatever value I set my terminal opacity to, it remains opaque.

On the other hand, I can set the opacity of the "normal" or the "bundled" Command Prompt and Powershell with no Windows issue.

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.175]
Windows Terminal version (if applicable): 0.2.1715.0

CPU
    Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz

GPU
    NVIDIA GeForce GT 710
    Driver version: 25.21.14.2531
    Driver date: 09/04/2019
    DirectX version: 12 (FL 11.0)
    Physical location: PCI bus 5, device 0, function 0

Steps to reproduce

  • Launch Windows Terminal on my machine :)
  • Go to Settings; Ctrl+,
  • Set acrylicOpacity to a value that is less than 1; e.g., 0.75 or 0.5

Expected behaviour

The window becomes semi-transparent.

Actual behaviour

The window is still opaque.

Originally created by @TheBlueSky on GitHub (Jun 22, 2019). Whatever value I set my terminal opacity to, it remains opaque. On the other hand, I can set the opacity of the "normal" or the "bundled" Command Prompt and Powershell with no Windows issue. # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.175] Windows Terminal version (if applicable): 0.2.1715.0 CPU Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GPU NVIDIA GeForce GT 710 Driver version: 25.21.14.2531 Driver date: 09/04/2019 DirectX version: 12 (FL 11.0) Physical location: PCI bus 5, device 0, function 0 ``` # Steps to reproduce - Launch Windows Terminal on my machine :) - Go to Settings; `Ctrl+,` - Set `acrylicOpacity` to a value that is less than 1; e.g., 0.75 or 0.5 # Expected behaviour The window becomes semi-transparent. # Actual behaviour The window is still opaque.
claunia added the Needs-Tag-FixNeeds-AttentionProduct-Terminal labels 2026-01-30 22:42:30 +00:00
claunia commented 2026-01-30 22:42:31 +00:00
Author
Owner
Copy Link

@Aulos commented on GitHub (Jun 22, 2019):

Try setting useAcrylic to true

@Aulos commented on GitHub (Jun 22, 2019): Try setting `useAcrylic` to `true`
claunia commented 2026-01-30 22:42:31 +00:00
Author
Owner
Copy Link

@TheBlueSky commented on GitHub (Jun 23, 2019):

@Aulos, thanks; haven't noticed the useAcrylic setting.

@TheBlueSky commented on GitHub (Jun 23, 2019): @Aulos, thanks; haven't noticed the `useAcrylic` setting.
claunia commented 2026-01-30 22:42:31 +00:00
Author
Owner
Copy Link

@fde-capu commented on GitHub (Dec 18, 2019):

Looking for simple transparency. Would it possible to implement parameter options for each Acrylic layer?

@fde-capu commented on GitHub (Dec 18, 2019): Looking for simple transparency. Would it possible to implement parameter options for each Acrylic layer?
claunia commented 2026-01-30 22:42:31 +00:00
Author
Owner
Copy Link

@MPeti1 commented on GitHub (May 7, 2020):

Looking for simple transparency. Would it possible to implement parameter options for each Acrylic layer?

Well it seems at Microsoft they are not willing to have any kind of opacaity other than acrylic. As far as I know the old opacity effects can't be reactivated, not even with registry hacks

@MPeti1 commented on GitHub (May 7, 2020): > > > Looking for simple transparency. Would it possible to implement parameter options for each Acrylic layer? Well it seems at Microsoft they are not willing to have any kind of opacaity other than acrylic. As far as I know the old opacity effects can't be reactivated, not even with registry hacks
claunia commented 2026-01-30 22:42:32 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 7, 2020):

not willing

If we weren’t willing, we would have closed #603 instead of leaving it open as the workitem tracking the request for traditional transparency.

@DHowett-MSFT commented on GitHub (May 7, 2020): > not willing If we weren’t willing, we would have closed #603 instead of leaving it open as the workitem tracking the request for traditional transparency.
claunia commented 2026-01-30 22:42:32 +00:00
Author
Owner
Copy Link

@MPeti1 commented on GitHub (May 9, 2020):

@DHowett-MSFT I'm not speaking of just this project. It's in beta, so it's not I speak of Windows too. You (or probably an other team working on an other part of the OS) took out the traditional transparency to put in the acrylic one. Why did you do that?

Edit: removed PS. The problem is still there, but it's probably caused by something else much deeper in the OS

@MPeti1 commented on GitHub (May 9, 2020): @DHowett-MSFT I'm not speaking of just this project. It's in beta, so it's not I speak of Windows too. You (or probably an other team working on an other part of the OS) took out the traditional transparency to put in the acrylic one. Why did you do that? Edit: removed PS. The problem is still there, but it's probably caused by something else much deeper in the OS
claunia commented 2026-01-30 22:42:32 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 11, 2020):

took out the traditional transparency to put in the acrylic one. Why did you do that?

Uh, no, we never took out the traditional transparency option. That's left totally unchanged in the vintage console host. We just haven't had the time to implement traditional opacity in a good fashion in the Terminal quite yet. That's the whole point of #603 - we want to add that functionality, but we'd rather not just do it in the janky "make the entire UI transparent like conhost did"

@zadjii-msft commented on GitHub (May 11, 2020): > took out the traditional transparency to put in the acrylic one. Why did you do that? Uh, no, we never took out the traditional transparency option. That's left totally unchanged in the vintage console host. We just haven't had the time to implement traditional opacity in a good fashion in the Terminal quite yet. That's the whole point of #603 - we _want_ to add that functionality, but we'd rather not just do it in the janky "make the entire UI transparent like conhost did"
claunia commented 2026-01-30 22:42:32 +00:00
Author
Owner
Copy Link

@MPeti1 commented on GitHub (May 11, 2020):

@zadjii-msft It seems I badly edited my comment. Or the GitHub app I use saved my edit badly

In that sentence I asked about Windows 10, not Windows Terminal

@MPeti1 commented on GitHub (May 11, 2020): @zadjii-msft It seems I badly edited my comment. Or the GitHub app I use saved my edit badly In that sentence I asked about Windows 10, not Windows Terminal
claunia commented 2026-01-30 22:42:32 +00:00
Author
Owner
Copy Link

@nathan-fiscaletti commented on GitHub (May 11, 2020):

The issue with Acrylic is that the transparency seems to go away when the window loses focus. Is there a way to fix this?

@nathan-fiscaletti commented on GitHub (May 11, 2020): The issue with Acrylic is that the transparency seems to go away when the window loses focus. Is there a way to fix this?
claunia commented 2026-01-30 22:42:33 +00:00
Author
Owner
Copy Link

@Gonkers commented on GitHub (May 15, 2020):

The acrylic options seem partially broken and or lackluster. Acrylic only seems to work when the window is in focus. In addition there does not appear to be a blur intensity setting. I would prefer to have nearly crystal clear like the classic terminal
image
I would actually use that as a feature to read text from a background window

@Gonkers commented on GitHub (May 15, 2020): The acrylic options seem partially broken and or lackluster. Acrylic only seems to work when the window is in focus. In addition there does not appear to be a blur intensity setting. I would prefer to have nearly crystal clear like the classic terminal ![image](https://user-images.githubusercontent.com/8480646/82018242-e152b500-9652-11ea-9868-5b652f1e344d.png) I would actually use that as a feature to read text from a background window
claunia commented 2026-01-30 22:42:33 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 15, 2020):

@Gonkers I believe these things were already covered in the thread above you. Thanks for your input!

@DHowett-MSFT commented on GitHub (May 15, 2020): @Gonkers I believe these things were already covered in the thread above you. Thanks for your input!
claunia commented 2026-01-30 22:42:33 +00:00
Author
Owner
Copy Link

@Gonkers commented on GitHub (May 15, 2020):

Sure thanks for the acknowledgement, but I guess the other part of the issue is a #WontFix https://github.com/microsoft/terminal/issues/593

Clearly this is a hot button issue. Sorry for wasting your time, I should have worked more on my google fu. Keep up the good fight. @DHowett-MSFT

@Gonkers commented on GitHub (May 15, 2020): Sure thanks for the acknowledgement, but I guess the other part of the issue is a #WontFix https://github.com/microsoft/terminal/issues/593 Clearly this is a hot button issue. Sorry for wasting your time, I should have worked more on my google fu. Keep up the good fight. @DHowett-MSFT
claunia commented 2026-01-30 22:42:34 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 15, 2020):

(We definitely want to support materials that don’t have the blur, or materials that stay visible when the window is inactive, but there’s only so many hours in a day. 😄)

@DHowett-MSFT commented on GitHub (May 15, 2020): (We definitely want to support materials that don’t have the blur, or materials that stay visible when the window is inactive, but there’s only so many hours in a day. :smile:)
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 Needs-Attention Needs-Tag-Fix 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#1942
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?