Fade effect behind close diaglogue covers part of the window #15899

Closed
opened 2026-01-31 04:51:38 +00:00 by claunia · 3 comments
Owner

Originally created by @AdrianDeWinter on GitHub (Nov 17, 2021).

Windows Terminal version

1.112921.0

Windows build number

19043.1348

Other Software

No response

Steps to reproduce

Open Terminal with more tah one tab.
Set the Window to fullscreen.
Attempt to close the window.
The "Do you want to close all tabs?" dialogue appears

Expected Behavior

The fade effect should cover the entire window behind the dialogue, not just a corner of it

Actual Behavior

Only a part of the window gets faded to white, specifically about a quarter in the top left corner, of roughly the the same size as the default terminal window

Originally created by @AdrianDeWinter on GitHub (Nov 17, 2021). ### Windows Terminal version 1.112921.0 ### Windows build number 19043.1348 ### Other Software _No response_ ### Steps to reproduce Open Terminal with more tah one tab. Set the Window to fullscreen. Attempt to close the window. The "Do you want to close all tabs?" dialogue appears ### Expected Behavior The fade effect should cover the entire window behind the dialogue, not just a corner of it ### Actual Behavior Only a part of the window gets faded to white, specifically about a quarter in the top left corner, of roughly the the same size as the default terminal window
claunia added the Resolution-Duplicate label 2026-01-31 04:51:38 +00:00
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Nov 17, 2021):

This is a duplicate of https://github.com/microsoft/terminal/issues/2380, which was closed as a duplicate of https://github.com/microsoft/microsoft-ui-xaml/issues/3577.

(Personally, I'm more used to a workflow where I keep an issue open in the affected project and mark it blocked by the issue in the other project. Not sure how well GitHub supports that, though.)

@KalleOlaviNiemitalo commented on GitHub (Nov 17, 2021): This is a duplicate of <https://github.com/microsoft/terminal/issues/2380>, which was closed as a duplicate of <https://github.com/microsoft/microsoft-ui-xaml/issues/3577>. (Personally, I'm more used to a workflow where I keep an issue open in the affected project and mark it blocked by the issue in the other project. Not sure how well GitHub supports that, though.)
Author
Owner

@zadjii-msft commented on GitHub (Nov 17, 2021):

More often than not, I usually do keep the issue on our side open, but also 🤷 That one's an OS-side bug so it's not like we'll need to ingest a new WinUI version to get the fix. When it gets ported to xaml islands and serviced, we should just magically stop hearing about this 😛

/dup #2380

@zadjii-msft commented on GitHub (Nov 17, 2021): More often than not, I usually do keep the issue on our side open, but also 🤷 That one's an OS-side bug so it's not like we'll need to ingest a new WinUI version to get the fix. When it gets ported to xaml islands and serviced, we should just magically stop hearing about this 😛 /dup #2380
Author
Owner

@ghost commented on GitHub (Nov 17, 2021):

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 (Nov 17, 2021): 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#15899