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

useAcrylic not applying to backgroundImage #22911

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

Originally created by @MarcoBuess on GitHub (Feb 12, 2025).

Windows Terminal version

1.22.10352.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

  1. Set "opacity": 0, "useAcrylic": true. This will set the acrylic effect as expected.
  2. Set "backgroundImage": "desktopWallpaper".
  3. Restart Terminal.
  4. See how the acrylic effekt has now disappeard.

Plaing around with backgroundImageOpacity doesn't achieve the same acrylic effect.

Expected Behavior

useAcrylic should also apply the effect on the configured backgroundImage.

Actual Behavior

The acrylic effect dissapears as if opacticy was set to 0 without any acrylic effect.

Originally created by @MarcoBuess on GitHub (Feb 12, 2025). ### Windows Terminal version 1.22.10352.0 ### Windows build number 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce 1. Set `"opacity": 0`, `"useAcrylic": true`. This will set the acrylic effect as expected. 2. Set `"backgroundImage": "desktopWallpaper"`. 3. Restart Terminal. 4. See how the acrylic effekt has now disappeard. Plaing around with `backgroundImageOpacity` doesn't achieve the same acrylic effect. ### Expected Behavior `useAcrylic` should also apply the effect on the configured `backgroundImage`. ### Actual Behavior The acrylic effect dissapears as if `opacticy` was set to `0` without any acrylic effect.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:26:55 +00:00
claunia commented 2026-01-31 08:26:56 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Feb 12, 2025):

We've found some similar issues:

  • #8410 , similarity score: 83%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Feb 12, 2025): We've found some similar issues: - #8410 , similarity score: 83% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
claunia commented 2026-01-31 08:26:56 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 12, 2025):

Thanks for filing! So, this is actually by design. The background image is applied on top of the acrylic material, so the acrylic effect shouldn't apply to the background image itself.

Curious, what are you trying to achieve here /? Do you want the acrylic applied on top of the image? Trying to better understand here 😊

@carlos-zamora commented on GitHub (Feb 12, 2025): Thanks for filing! So, this is actually by design. The background image is applied on top of the acrylic material, so the acrylic effect shouldn't apply to the background image itself. Curious, what are you trying to achieve here /? Do you want the acrylic applied on top of the image? Trying to better understand here 😊
claunia commented 2026-01-31 08:26:56 +00:00
Author
Owner
Copy Link

@MarcoBuess commented on GitHub (Feb 12, 2025):

Exactly. I like the looks of the effect which I think can't be mimiced by backgroundImageOpacity.

@MarcoBuess commented on GitHub (Feb 12, 2025): Exactly. I like the looks of the effect which I think can't be mimiced by `backgroundImageOpacity`.
claunia commented 2026-01-31 08:26:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 12, 2025):

Thanks for explaining!

This isn't something we're likely to invest in - it'll probably harm performance and our background image stack is complicated enough.

For right now, pre-baking your image will unfortunately need to suffice.

@DHowett commented on GitHub (Mar 12, 2025): Thanks for explaining! This isn't something we're likely to invest in - it'll probably harm performance and our background image stack is complicated enough. For right now, pre-baking your image will unfortunately need to suffice.
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-Attention Needs-Triage
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#22911
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?