Windows Terminal doesn't show dynamic content when transparency is enabled #18741

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

Originally created by @SerhiiRohoza on GitHub (Oct 21, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

No response

Other Software

No response

Steps to reproduce

  1. Turn on transparency
  2. Play video or dynamically updated log file in another window
  3. Look on the dynamic content via transparent Widows Terminal and find that it's not updating accordingly

Expected Behavior

Widows Terminal should allows me to see updated content from the background application when transparency is enabled.

Actual Behavior

Windows Terminal shows only static picture when transparency is enabled.

Originally created by @SerhiiRohoza on GitHub (Oct 21, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number _No response_ ### Other Software _No response_ ### Steps to reproduce 1. Turn on transparency 2. Play video or dynamically updated log file in another window 3. Look on the dynamic content via transparent Widows Terminal and find that it's not updating accordingly ### Expected Behavior Widows Terminal should allows me to see updated content from the background application when transparency is enabled. ### Actual Behavior Windows Terminal shows only static picture when transparency is enabled.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:23:02 +00:00
Author
Owner

@DHowett commented on GitHub (Oct 21, 2022):

Two additional questions:

  1. What version of Windows are you on? I see that you did not include it in the original issue.
  2. What application is behind Terminal?

Some applications detect that there is a window in front of them and stop updating (or update more slowly.) This is by design for those applications, and Terminal cannot trick then into updating.

@DHowett commented on GitHub (Oct 21, 2022): Two additional questions: 1. What version of Windows are you on? I see that you did not include it in the original issue. 2. What application is behind Terminal? Some applications detect that there is a window in front of them and stop updating (or update more slowly.) This is by design for those applications, and Terminal cannot trick then into updating.
Author
Owner

@SerhiiRohoza commented on GitHub (Oct 21, 2022):

Two additional questions:

  1. What version of Windows are you on? I see that you did not include it in the original issue.
  2. What application is behind Terminal?

Some applications detect that there is a window in front of them and stop updating (or update more slowly.) This is by design for those applications, and Terminal cannot trick then into updating.

Please find more information below:

  1. I'm using Windows 11 21H2
  2. For example Google Chrome with a tab showing Google Cloud Platform running some build in Cloud Build or streaming Cloud Logging a ton of logs I'd like to see when doing something in Windows Terminal with GCP resources.
@SerhiiRohoza commented on GitHub (Oct 21, 2022): > Two additional questions: > > 1. What version of Windows are you on? I see that you did not include it in the original issue. > 2. What application is behind Terminal? > > Some applications detect that there is a window in front of them and stop updating (or update more slowly.) This is by design for those applications, and Terminal cannot trick then into updating. Please find more information below: 1. I'm using Windows 11 21H2 2. For example Google Chrome with a tab showing Google Cloud Platform running some build in Cloud Build or streaming Cloud Logging a ton of logs I'd like to see when doing something in Windows Terminal with GCP resources.
Author
Owner

@DHowett commented on GitHub (Oct 21, 2022):

Thanks!

Somebody filed a similar bug in #14059 and found the "magic words" to configure Chrome to ignore occlusion. They also followed up with instructions for Firefox. Both of those fixed start here: https://github.com/microsoft/terminal/issues/14059#issuecomment-1255772563

I'm gonna call this a /duplicate of #14059, with fixed noted. 😄

@DHowett commented on GitHub (Oct 21, 2022): Thanks! Somebody filed a similar bug in #14059 and found the "magic words" to configure Chrome to ignore occlusion. They also followed up with instructions for Firefox. Both of those fixed start here: https://github.com/microsoft/terminal/issues/14059#issuecomment-1255772563 I'm gonna call this a /duplicate of #14059, with fixed noted. 😄
Author
Owner

@ghost commented on GitHub (Oct 21, 2022):

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 (Oct 21, 2022): 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#18741