Default value of background image stretch mode is fill instead of uniformToFill #11384

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

Originally created by @CookieHCl on GitHub (Nov 13, 2020).

Environment

Windows build number: Microsoft Windows NT 10.0.19042.0
Windows Terminal version (if applicable): 1.4.3141.0, installed from chocolatey

Steps to reproduce

Add a background image to profile settings.
Don't set backgroundImageStretchMode so it can have default value.

Expected behavior

Background image should stretch like uniformToFill, because according to the documentation, this is the default value of backgroundImageStretchMode.

Actual behavior

Background image stretch like fill.

uniformToFill setting works if you explicitely set backgroundImageStretchMode, but it won't work in default value.

Originally created by @CookieHCl on GitHub (Nov 13, 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: Microsoft Windows NT 10.0.19042.0 Windows Terminal version (if applicable): 1.4.3141.0, installed from chocolatey ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Add a background image to profile settings. Don't set `backgroundImageStretchMode` so it can have default value. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Background image should stretch like `uniformToFill`, because according to the [documentation](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-settings#background-image-settings), this is the default value of `backgroundImageStretchMode`. # Actual behavior <!-- What's actually happening? --> Background image stretch like `fill`. `uniformToFill` setting works if you explicitely set `backgroundImageStretchMode`, but it won't work in default value.
Author
Owner

@Don-Vito commented on GitHub (Nov 13, 2020):

@CookieHCl - Yep.. in the code the default behavior of BackgroundImageStretchMode within Profile is Fill.
I guess this is not intentional, as in TerminalSettings the default is UniformToFill (but it gets overridden by Profile).
I am not an owner or an expert but If you want to contribute a fix for it I will gladly assist.

@Don-Vito commented on GitHub (Nov 13, 2020): @CookieHCl - Yep.. in the code the default behavior of BackgroundImageStretchMode within Profile is Fill. I guess this is not intentional, as in TerminalSettings the default is UniformToFill (but it gets overridden by Profile). I am not an owner or an expert but If you want to contribute a fix for it I will gladly assist.
Author
Owner

@zadjii-msft commented on GitHub (Nov 13, 2020):

Oh well that's weird, and definitely not intentional. Good catch!

@zadjii-msft commented on GitHub (Nov 13, 2020): Oh well that's weird, and definitely not intentional. Good catch!
Author
Owner

@ghost commented on GitHub (Nov 20, 2020):

:tada:This issue was addressed in #8280, which has now been successfully released as Windows Terminal v1.4.3243.0.🎉

Handy links:

@ghost commented on GitHub (Nov 20, 2020): :tada:This issue was addressed in #8280, which has now been successfully released as `Windows Terminal v1.4.3243.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.4.3243.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Author
Owner

@ghost commented on GitHub (Nov 20, 2020):

:tada:This issue was addressed in #8280, which has now been successfully released as Windows Terminal Preview v1.5.3242.0.🎉

Handy links:

@ghost commented on GitHub (Nov 20, 2020): :tada:This issue was addressed in #8280, which has now been successfully released as `Windows Terminal Preview v1.5.3242.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.5.3242.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11384