-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Settings] Window transparent without applying acrylic #12014
Comments
Acrylic depends on windows theme transparency (enabled or not). I don't use "Settings Page" because it changes formatting of settings.json. I prefer to make changes directly to the file.
|
How can I enable theme transparency on windows10? The one example above is from win 11 and it works fine, but for windows 10 I'm yet to figure out how to enable transparency without acrylic.' (Same thing happens when I change it in the settings.json) |
I have no way to check. |
Nope, does not work. |
Pure transparency (i.e. without acrylic) is currently only supported in Windows 11 because of a bug in XAML Islands. However there are plans to backport the fix to Windows 10. For more details, see #11180 (comment). |
Thank you, this answers my qustion! |
Looks like what you're seeing is /dup #11555, which should be fixed in the next build |
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! |
Windows Terminal version
1.12.3472.0
Windows build number
10.0.22000
Other Software
No response
Steps to reproduce
Settings > Default > Appearence > Transperancy
Expected Behavior
Changing the Transparency toggles acrylic to enabled.
Actual Behavior
Does not change to acrylic my window is transparent.
On my work pc (with windows 10 and no dedicated GPU) everytime I change the transparency it does toggle the acrylic also. There is no way to have the terminal transparent in that case.
Not 100% sure if that is intended, could not find a changelog about it.
The text was updated successfully, but these errors were encountered: