Ctrl+Shift+Scrollwheel can no longer fully disable transparency when using Acrylic #17215

Closed
opened 2026-01-31 05:35:41 +00:00 by claunia · 4 comments
Owner

Originally created by @kevinmyexp on GitHub (Apr 10, 2022).

Windows Terminal version

1.12.10733.0

Windows build number

10.0.22000.593

Other Software

No response

Steps to reproduce

"useAcrylic": true
"opacity": 100 / "acrylicOpacity": 1.0

Expected Behavior

Terminal window with fully opaque, solid color background

Actual Behavior

image

Terminal window still presents minor Acrylic effect,
thus making switch between Acrylic% and Opaque with C+S+Wheel impossible.

Originally created by @kevinmyexp on GitHub (Apr 10, 2022). ### Windows Terminal version 1.12.10733.0 ### Windows build number 10.0.22000.593 ### Other Software _No response_ ### Steps to reproduce "useAcrylic": true "opacity": 100 / "acrylicOpacity": 1.0 ### Expected Behavior Terminal window with fully opaque, solid color background ### Actual Behavior ![image](https://user-images.githubusercontent.com/17904156/162637785-4622852d-0881-4d03-bd50-6e0abd756358.png) Terminal window still presents minor Acrylic effect, thus making switch between Acrylic% and Opaque with C+S+Wheel impossible.
Author
Owner

@zadjii-msft commented on GitHub (Sep 14, 2022):

we discussed this some weeks back but never noted it down: I did this intentionally so people could have fully opaque acrylic. Turns out though, no one really likes that, and wants 100% opacity to always mean "acrylic off". That's fine by me. We just need to revert that bit of logic.

@zadjii-msft commented on GitHub (Sep 14, 2022): we discussed this some weeks back but never noted it down: I did this intentionally so people could have fully opaque acrylic. Turns out though, no one really likes that, and wants 100% opacity to always mean "acrylic off". That's fine by me. We just need to revert that bit of logic.
Author
Owner

@ofek commented on GitHub (Oct 4, 2022):

We just need to revert that bit of logic.

Would that be easy enough to include in the next release?

@ofek commented on GitHub (Oct 4, 2022): > We just need to revert that bit of logic. Would that be easy enough to include in the next release?
Author
Owner

@ghost commented on GitHub (Dec 14, 2022):

:tada:This issue was addressed in #14193, which has now been successfully released as Windows Terminal v1.15.3465.0 and v1.15.3466.0.🎉

Handy links:

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

@ghost commented on GitHub (Dec 14, 2022):

:tada:This issue was addressed in #14193, which has now been successfully released as Windows Terminal Preview v1.16.3463.0 and v1.16.3464.0.🎉

Handy links:

@ghost commented on GitHub (Dec 14, 2022): :tada:This issue was addressed in #14193, which has now been successfully released as `Windows Terminal Preview v1.16.3463.0 and v1.16.3464.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.16.3464.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#17215