Background image not shown when "antialiasingMode": "cleartype", "useAcrylic": false #11599

Closed
opened 2026-01-31 02:52:09 +00:00 by claunia · 6 comments
Owner

Originally created by @ks2k2d on GitHub (Nov 26, 2020).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.4.3243.0

Any other software?

Steps to reproduce

"antialiasingMode": "cleartype", "useAcrylic": false, "backgroundImage": "...some_file"

Expected behavior

Opaque image is shown as background

Actual behavior

Black background is shown and the image is visible only around the padding.
image

Originally created by @ks2k2d on GitHub (Nov 26, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- 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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 1.4.3243.0 Any other software? ``` # Steps to reproduce "antialiasingMode": "cleartype", "useAcrylic": false, "backgroundImage": "...some_file" # Expected behavior Opaque image is shown as background # Actual behavior Black background is shown and the image is visible only around the padding. ![image](https://user-images.githubusercontent.com/67361981/100348953-5c2c5d80-2ff0-11eb-8bd5-f131959e339a.png)
claunia added the Resolution-Duplicate label 2026-01-31 02:52:09 +00:00
Author
Owner

@pinxau1000 commented on GitHub (Nov 26, 2020):

For me everything worked as expected.

example:

{
                "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
                "hidden": false,
                "name": "Ubuntu",
                "source": "Windows.Terminal.Wsl",
		"commandline": "wsl -d Ubuntu",
		"tabTitle": "Ubuntu",
		"acrylicOpacity":0.75,
		"closeOnExit":true,
		"colorScheme":"Campbell",
		"fontFace":"Consolas",
		"fontSize":12,
		"historySize":9001,
		"backgroundImage": "<PATH>",
		"backgroundImageStretchMode": "none",
		"backgroundImageOpacity": 0.1,
		"icon":"<PATH>",
		"padding":"0, 0, 0, 0",
		"snapOnInput":true,
		"useAcrylic":false
}

ubuntu_windowsTerminal_3

@pinxau1000 commented on GitHub (Nov 26, 2020): For me everything worked as expected. example: ```json { "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}", "hidden": false, "name": "Ubuntu", "source": "Windows.Terminal.Wsl", "commandline": "wsl -d Ubuntu", "tabTitle": "Ubuntu", "acrylicOpacity":0.75, "closeOnExit":true, "colorScheme":"Campbell", "fontFace":"Consolas", "fontSize":12, "historySize":9001, "backgroundImage": "<PATH>", "backgroundImageStretchMode": "none", "backgroundImageOpacity": 0.1, "icon":"<PATH>", "padding":"0, 0, 0, 0", "snapOnInput":true, "useAcrylic":false } ``` ![ubuntu_windowsTerminal_3](https://user-images.githubusercontent.com/31994143/100354024-6007b200-2fe7-11eb-9985-0f024815c829.png)
Author
Owner

@ks2k2d commented on GitHub (Nov 26, 2020):

One difference I see between you and my case is that I have specified the configuration in the "defaults" section.

Moved the config to the WSL section of Ubuntu, but still doesn't work.

@ks2k2d commented on GitHub (Nov 26, 2020): One difference I see between you and my case is that I have specified the configuration in the "defaults" section. Moved the config to the WSL section of Ubuntu, but still doesn't work.
Author
Owner

@ks2k2d commented on GitHub (Nov 26, 2020):

It is not caused only by "useAcrylic": false
instead it is caused by the combination of "useAcrylic": false and "antialiasingMode": "cleartype"
I will update the description.

@ks2k2d commented on GitHub (Nov 26, 2020): It is not caused only by "useAcrylic": false instead it is caused by the combination of "useAcrylic": false and "antialiasingMode": "cleartype" I will update the description.
Author
Owner

@pinxau1000 commented on GitHub (Nov 26, 2020):

Indeed. Background image didn't shows when "useAcrylic": false and "antialiasingMode": "cleartype".

@pinxau1000 commented on GitHub (Nov 26, 2020): Indeed. Background image didn't shows when ```"useAcrylic": false``` and ```"antialiasingMode": "cleartype"```.
Author
Owner

@zadjii-msft commented on GitHub (Dec 2, 2020):

Thanks for the report and the investigation! It looks to me like this is the same root cause as #5703, so I'll redirect discussion to that thread. Thanks!

/dup #5703

@zadjii-msft commented on GitHub (Dec 2, 2020): Thanks for the report and the investigation! It looks to me like this is the same root cause as #5703, so I'll redirect discussion to that thread. Thanks! /dup #5703
Author
Owner

@ghost commented on GitHub (Dec 2, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Dec 2, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11599