starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-23 23:45:08 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Enable a background image on top of an acrylic brush #1434

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

Originally created by @SJang1 on GitHub (May 31, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.18908.1000]
Windows Terminal version (if applicable): commit id d24d647 and 71e19cd tested.

Steps to reproduce

add "backgroundImage" to profiles.

Expected behavior

Backgroung Image changes to what I have selected.

Actual behavior

Only Powershell works as expected, cmd, ubuntu, ... doesn't work like image I've pasted. (Just stays as normal)
image

Originally created by @SJang1 on GitHub (May 31, 2019). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18908.1000] Windows Terminal version (if applicable): commit id d24d647 and 71e19cd tested. ``` # Steps to reproduce add "backgroundImage" to profiles. # Expected behavior Backgroung Image changes to what I have selected. # Actual behavior Only Powershell works as expected, cmd, ubuntu, ... doesn't work like image I've pasted. (Just stays as normal) ![image](https://user-images.githubusercontent.com/29011440/58688033-4bc90180-83be-11e9-91f4-a964fee27345.png)
claunia commented 2026-01-30 22:27:01 +00:00
Author
Owner
Copy Link

@Summon528 commented on GitHub (May 31, 2019):

The current implementation of background image requires you to disable acrylic

@Summon528 commented on GitHub (May 31, 2019): The current implementation of background image requires you to disable acrylic
claunia commented 2026-01-30 22:27:01 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (May 31, 2019):

When a background image is set, the acrylic should not be disabled. Instead the acrylic brush should change from a backdrop host one, to an in app one. This will then blur the background image and not show what is behind the window

@mdtauk commented on GitHub (May 31, 2019): When a background image is set, the acrylic should not be disabled. Instead the acrylic brush should change from a **backdrop** host one, to an **in app** one. This will then blur the background image and not show what is behind the window
claunia commented 2026-01-30 22:27:02 +00:00
Author
Owner
Copy Link

@Summon528 commented on GitHub (May 31, 2019):

When a background image is set, the acrylic should not be disabled. Instead the acrylic brush should change from a backdrop host one, to an in app one. This will then blur the background image and not show what is behind the window

Yeah that is the ideal solution. However this is an unimplemented feature, rather than a bug for now. Core dev did mention to file a follow-up issue for this feature https://github.com/microsoft/terminal/pull/853#pullrequestreview-241953563 but apparently that has not been done yet

@Summon528 commented on GitHub (May 31, 2019): > > > When a background image is set, the acrylic should not be disabled. Instead the acrylic brush should change from a **backdrop** host one, to an **in app** one. This will then blur the background image and not show what is behind the window Yeah that is the ideal solution. However this is an unimplemented feature, rather than a bug for now. Core dev did mention to file a follow-up issue for this feature https://github.com/microsoft/terminal/pull/853#pullrequestreview-241953563 but apparently that has not been done yet
claunia commented 2026-01-30 22:27:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 31, 2019):

Congratulations, this is now that follow-up

@zadjii-msft commented on GitHub (May 31, 2019): Congratulations, this is now that follow-up
claunia commented 2026-01-30 22:27:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 3, 2019):

Thought: to make this a little better, we might want to implement something like "background stacks" -- so you can specify:

background: [
  { ... acrylic host backdrop ... }
  { ... image tux.exe ... }
  { ... acrylic app-backdrop ... }
]

Marking this as Issue-Feature?

@DHowett-MSFT commented on GitHub (Jun 3, 2019): Thought: to make this a little better, we might want to implement something like "background stacks" -- so you can specify: ``` background: [ { ... acrylic host backdrop ... } { ... image tux.exe ... } { ... acrylic app-backdrop ... } ] ``` Marking this as Issue-Feature?
claunia commented 2026-01-30 22:27:03 +00:00
Author
Owner
Copy Link

@isaacrlevin commented on GitHub (Jun 24, 2019):

If I am following this, the following experience is not supported.

  • Image with transparent background over a solid background

I have tried a few combinations of settings to no avail

@isaacrlevin commented on GitHub (Jun 24, 2019): If I am following this, the following experience is not supported. - Image with transparent background over a solid background I have tried a few combinations of settings to no avail
claunia commented 2026-01-30 22:27:04 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 24, 2019):

Indeed. This will hopefully fix that issue as well.

@DHowett-MSFT commented on GitHub (Jun 24, 2019): Indeed. This will hopefully fix that issue as well.
claunia commented 2026-01-30 22:27:04 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (Jun 24, 2019):

On top of acrylic, it is more of a watermark. It would also need a placement option.

@mdtauk commented on GitHub (Jun 24, 2019): On top of acrylic, it is more of a watermark. It would also need a placement option.
claunia commented 2026-01-30 22:27:04 +00:00
Author
Owner
Copy Link

@Jaykul commented on GitHub (Jun 26, 2019):

We definitely need a placement option

@Jaykul commented on GitHub (Jun 26, 2019): We definitely need a placement option
claunia commented 2026-01-30 22:27:04 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 3, 2019):

:tada:This issue was addressed in #1107, which has now been successfully released as Windows Terminal Preview v0.3.2142.0.🎉

Handy links:

@ghost commented on GitHub (Aug 3, 2019): :tada:This issue was addressed in #1107, which has now been successfully released as `Windows Terminal Preview v0.3.2142.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.3.2142.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
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-Settings Area-TerminalControl Help Wanted Issue-Feature Needs-Tag-Fix Product-Terminal Resolution-Fix-Committed
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#1434
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?